View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0025680||mantisbt||bugtracker||public||2019-04-04 23:01||2019-04-25 18:42|
|Summary||0025680: Redirect after bug report process ending|
There is a g_default_home_page configuration parameter.
|Tags||No tags attached.|
That makes sense and would be consistent with the concept of "default page".
I'm not sure... currently, "default page" is the landing page after login.
...not consistent, but still it's a related page in that context.
I see that a common setting for "default page" can be "my view" page. I wouldn't like to go to "my view" after each issue creation. I'd expect it to go to view issues list, or the individual new issue.
There is another option.
What do you think?
I updated my PR.
Now you can take into account the wishes of @cproensa and redirect to the page from which the process started reporting the error.
To register the page of the parent, I used cookies.
Unfortunately, there is a small feature. We cannot control the cancellation of the creation issue, and therefore the cookie will not be cleared. That will lead to a one-time violation of logic in the redirection process. It seems to me that this will happen quite rarely.
What do you think?
I'm not really fond of this implementation with cookies. Do we really need to go back to wherever the new bug was submitted ?
The more I think about it, and considering my usage of the system, over 95% of the times after submitting a new issue, I want to see it afterwards. Sometimes I want to create another issue right after that (which is achieved by the Report Stay check box on the bug report page, and if I forget I just click on the Report Issue button on the sidebar again). Occasionally I want to see the issues list; this is currently the default behavior on bug_report.php after timeout, maybe we should change that ?
Anyway, I'm tempted to close this as "won't fix". Thoughts ?
Well, there is another option.
What if we configure the global parameter 'default_home_page' for each user?
@123 I was more questioning the use case for allowing user to pick the target page after submitting a but, more than the proposed implementation itself.
My point is that this adds complexity for no or very little benefit, and we should stick to current behavior or even simplify it (i.e. always return to the newly created issue's page). Most key MantisBT pages are just one click away from that anyway.
Maybe you care to explain your reasons for needing this feature.
@dregad As I wrote below, I will be satisfied with the redirect to default_home_page.
With my suggestion for improving this part of the code, I wanted to achieve the logical behavior of the mantisbt.
Also in my use case mantisbt I would really like to be able to remove the link to view_all_bug_page from the side menu, since for most users it is not needed. This page is used only if it is necessary to sort the issues by a specific filter and only engineers use it, and in rare cases.
While I don't necessarily disagree with this, I personally don't think it is useful as per my earlier comment.
Which contradicts his previous statement.
Considering that you
then I think we are in agreement ?
While I would agree that its usage could be considered complex and not so useful for some literate people, this page is quite central to MantisBT operations, and I would recommend against removing it, as this is the only way to access issues globally and to search / filter them.
I'm sorry, I incorrectly formulated my answer.
Last question. Do we change the behavior of buttons on bug_report.php or leave everything as it is?
@123 thanks for your feedback.
I propose the following :
Optionally, change defaut redirect from view_all_bug_page.php to the newly opened bug's page, which IMO is more useful (a separate issue should be created for that).
Note that the "report stay" option will add a 3rd button to this page to report more issues, and change default redirect to bug_report_page.php
Alternatively, I would be also fine with not presenting any buttons to the user, and just automatically redirect to view.php or bug_report_page.php depending on status of "Report Stay" checkbox.
|2019-04-04 23:01||123||New Issue|
|2019-04-04 23:04||123||Note Added: 0061832|
|2019-04-05 06:07||dregad||Note Added: 0061835|
|2019-04-05 20:26||cproensa||Note Added: 0061839|
|2019-04-05 21:27||123||Note Added: 0061840|
|2019-04-09 05:36||123||Note Added: 0061869|
|2019-04-13 12:04||dregad||Assigned To||=> community|
|2019-04-13 12:04||dregad||Status||new => assigned|
|2019-04-13 12:12||dregad||Note Added: 0061923|
|2019-04-13 21:38||123||Note Added: 0061927|
|2019-04-14 12:46||dregad||Note Added: 0061931|
|2019-04-14 23:18||123||Note Added: 0061932|
|2019-04-14 23:24||123||Note Edited: 0061932||View Revisions|
|2019-04-15 02:39||dregad||Note Added: 0061933|
|2019-04-15 05:45||123||Note Added: 0061935|
|2019-04-15 05:50||123||Note Added: 0061936|
|2019-04-15 06:01||123||Note Edited: 0061935||View Revisions|
|2019-04-15 06:52||dregad||Note Added: 0061937|
|2019-04-16 01:09||123||Note Added: 0061940|
|2019-04-16 01:31||123||Issue cloned: 0025695|
|2019-04-16 01:31||123||Relationship added||related to 0025695|
|2019-04-16 05:25||dregad||Assigned To||community => dregad|
|2019-04-16 05:25||dregad||Status||assigned => resolved|
|2019-04-16 05:25||dregad||Resolution||open => won't fix|
|2019-04-25 18:42||atrol||Status||resolved => closed|