View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005649 | mantisbt | relationships | public | 2005-05-25 11:47 | 2023-10-30 15:34 |
Reporter | gtomlin | Assigned To | dregad | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Product Version | 1.0.0a2 | ||||
Summary | 0005649: Existing 'duplicate of' bug number not displayed on bug_change_status_page.php when resolving | ||||
Description | If bug 2 has been marked as a duplicate of bug 1 in the Relationships section, and then the user goes to resolve issue 2, issue 1 is not displayed in the "Duplicate ID" field on bug_change_status_page.php; this means the user has to have either memorized/recorded the original bug ID or must go back to view the bug being resolved to see what the original ID was. | ||||
Tags | No tags attached. | ||||
Adding an existing duplicate bug ID is fine, but what should the system do in the case where if there are multiple duplicates issues ? |
|
This has been made redundant by 0010059 (fixed in release 1.3.0), which automatically sets the resolution to duplicate and hides the Duplicate Id field if the Issue at least one |
|