View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005563 | mantisbt | bugtracker | public | 2005-05-03 11:00 | 2025-01-10 11:33 |
Reporter | garethfiler | Assigned To | dregad | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | resolved | Resolution | no change required | ||
Product Version | 1.0.0a2 | ||||
Summary | 0005563: Reverting a bug back to Resolved when the bug was closed | ||||
Description | Should I be able to revert a closed bug back to Resolved when a bug had previously been closed? I had a bug which was set to closed.
I would have though you would have stopped the issue 00001 being set back to any other state before closed. And maybe force the user to create another issue which can then have a relationship to the closed issue??? I hope this makes sence, if not please email me. | ||||
Tags | No tags attached. | ||||
You should not be able to mark an issue as a duplicate of itself when resolving it. An error should result and the issues will be left as they were. Was the issue closed when you started this process? |
|
According to the description, the bug was closed when they started the process. It looks like from the view simple screen, they changed the status to resolved, on the next screen related it to itself, and then successfully submitted it. So, an issue should not be allowed to be related to itself (as noted above). Setting it back to another state once closed is and should be configurable based on login type, right? |
|
The ability to change from one status to another is controlled by the workflow. If you try to relate an issue to itself, Mantis will throw APPLICATION ERROR 1101 You cannot set an issue as a duplicate of itself. Resolving this as "no change required". |
|