View Issue Details

IDProjectCategoryView StatusLast Update
0032893mantisbtuipublic2023-09-09 16:09
Reportervboctor Assigned Tovboctor  
PrioritynormalSeverityminorReproducibilityN/A
Status closedResolutionduplicate 
Product Version2.25.6 
Summary0032893: Retire "Operation Successful" pages
Description

I suggest retiring this for the following reasons:

  • It is very old behavior.
  • It is very slow compared to a direct redirect due to the delay we introduce.
  • It disrupts the user flow, specially if they are doing multiple actions on a page.

I think we can start by having print_successful_redirect() deprecated and make it just call print_header_redirect().

I also think we should retire the one after reporting an issue which gives user options to go to the issue or View Issues page. I would just go to the view issue page of the created issue.

@dregad @atrol thoughts?

TagsNo tags attached.

Relationships

duplicate of 0005189 closedvboctor "Operation successful." message page slows down interaction 
related to 0021109 closeddregad Replace "operational successful" pages with flash control 

Activities

dregad

dregad

2023-08-30 04:17

developer   ~0068048

I'm OK with this.

Do we need to introduce some other kind of visual feedback that the update was successful ? E.g. some kind of javascript-driven pop-up in the target page, that goes away after a couple of seconds ? Or do you think the absence of an error message implies success, and it's enough like that ?

retire the one after reporting an issue which gives user options to go to the issue or View Issues page. I would just go to the view issue page of the created issue.

Sounds good.

This would probably make $g_default_redirect_delay (and related user preference) obsolete.

atrol

atrol

2023-08-30 04:35

developer   ~0068049

Last edited: 2023-08-30 04:36

I'm also OK with this.

Do we need to introduce some other kind of visual feedback that the update was successful ?

Not sure, sometimes these Flash Popups can be annyoing, seems that Victor planned the same 0021109

dregad

dregad

2023-08-30 05:03

developer   ~0068050

Thanks for researching and linking related issues. This one should probably be closed as duplicate in favor of 0005189...