View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004224 | mantisbt | relationships | public | 2004-07-30 14:34 | 2004-11-06 06:24 |
Reporter | pdugas | Assigned To | masc | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 0.19.0a2 | ||||
Fixed in Version | 0.19.1 | ||||
Summary | 0004224: Can't resolve issue as duplicate of other with existing "related to" relationship | ||||
Description | Doing some tinkering demonstrating the system to a customer and ran accross this one. I created two issues and a "related to" relationship between them. If I try to resolve either of them, select "duplicate" for the resolution, and enter the id of the other; I get "APPLICATION ERROR 0001800" "ERROR: There is already a relationship between these two issues." | ||||
Tags | No tags attached. | ||||
This is by design, two issues can have only one relationship between them. If you want to change a relationship to another, then you have to delete the old one and add a new one. In this case, delete the "related-to" and add "duplicate". |
|
Perhaps a more suitable and explanatory error message is in order? "APPLICATION ERROR" and "by design" don't seem to jive. ;) |
|
In the actual implementation you can resolve a bug as duplicate of an other is between the two bugs are no relationship or, if it exists, it's the right duplicate relationship. In your case the relationship was "related to", for this the error message. |
|
Inviato memorandum a VictorBoctor Victor, |
|
Inviato memorandum a vboctor Victor, |
|
In my opinion, if we do that then we should do it as follows:
Ideally, the user should get a warning when overwritting an exist relationship, but this is a nice to have (in my opinion). |
|
Patch from Masc For this issue and other issues committed: |
|
MantisBT: master 3df7d2c5 2004-10-05 17:12 Paul Richards Details Diff |
Commit of Masc's Patches: Fix 0004506: When cloning a bug you should be able to set the relationship Fix 0004484: Show which project a related issue belongs to Fix 0004184: Related issues resolved email should be more informative Fix 0004224: Can't resolve issue as duplicate of other with existing "related to" relationship git-svn-id: http://mantisbt.svn.sourceforge.net/svnroot/mantisbt/trunk@3037 <a class="text" href="/?p=mantisbt.git;a=object;h=f5dc347c">f5dc347c</a>-c33d-0410-90a0-b07cc1902cb9 |
Affected Issues 0004184, 0004224, 0004484, 0004506 |
|
mod - core/relationship_api.php | Diff File | ||
mod - core/email_api.php | Diff File | ||
mod - bug_relationship_delete.php | Diff File | ||
mod - lang/strings_italian.txt | Diff File | ||
mod - bug_report_page.php | Diff File | ||
mod - core/bug_api.php | Diff File | ||
mod - bug_relationship_add.php | Diff File | ||
mod - core/constant_inc.php | Diff File | ||
mod - bug_report.php | Diff File | ||
mod - bug_report_advanced_page.php | Diff File | ||
mod - core/history_api.php | Diff File | ||
mod - lang/strings_english.txt | Diff File |