View Issue Details

IDProjectCategoryView StatusLast Update
0023404mantisbtotherpublic2017-10-04 17:04
Reporterhelfy022 Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
Status newResolutionopen 
Product Version2.5.1 
Summary0023404: page following bug move
Description

Hello,

After moving a bug, the user is brought to the View Issues page as opposed to the View Issue Details page (as, for instance, the clone operation give the user the option of viewing). Is this expected? Is it possible to tune the config to ensure that the user can navigate to the View Issue Details page for the just-moved bug?

Please let me know if you need any more information in order to understand the situation.

Thanks,
Ryan.

TagsNo tags attached.

Activities

atrol

atrol

2017-09-27 15:38

developer   ~0057829

There is no configuration option for it.

helfy022

helfy022

2017-09-27 16:07

reporter   ~0057830

Thanks, @atrol. Should I assume, then, that this is the expected sequence, and to modify would involve something invasive (e.g., a plug-in, or touching the core infrastructure)?

Thanks,
Ryan.

atrol

atrol

2017-09-27 16:23

developer   ~0057831

and to modify would involve something invasive (e.g., a plug-in, or touching the core infrastructure)?

Right at the moment.

Feel free to send us a pull request on Github if you want it changed in standard Mantis.

helfy022

helfy022

2017-10-04 16:45

reporter   ~0057894

Hi @atrol,

Thanks for the information. Just to make sure I understand the next steps, would a Github pull request imply that I submit the actual code changes? Or, would the enhancement request to bring about the noted behavior be filed in the form of a Github pull request (as opposed to an enhancement request here in the support bug-tracker)?

Thanks,
Ryan.

atrol

atrol

2017-10-04 17:04

developer   ~0057895

would a Github pull request imply that I submit the actual code changes?

Right, https://help.github.com/articles/creating-a-pull-request/