Relationships clarification
Moderators: Developer, Contributor
Relationships clarification
I thought I could duplicate issue "X" on issue "Y" and when closing issue "Y" automatically close also the issue "X" since it is duplicated, but this is not the case. Can you clarify what is the reason behind this choice? Am I missing something?
Re: Relationships clarification
We often have different symptoms of the same problem reported as different issues. They get duplicated to one issue. I close an issue after I verify the fix. At the same time, I usually go through all the duplicates, verifying the different scenarios in there (and if there's nothing that differs from the main issue, I'd close the dupe at duplication time). Sometimes what was thought to be a dupe ends up being a separate bug in this step, sometimes the main fix needs to be enhanced and I re-open the main issue.
Re: Relationships clarification
My thoughts on duplicates are this.
If issue Y is submitted and it is determined that it is a duplicate of issue X, I would:
1) Try and determine if there is any useful information in Y that is not in X.
1a) If so, try and integrate the new information from Y into X (through the additional information field, or a bugnote perhaps).
2) Create a relationship so Issue Y is a "duplicate of" Issue X (not the other way around).
3) Give Issue Y a resolution of "duplicate".
4) Make Issue Y read-only to prevent new information being added to it. Unfortunately, only way I know to do this is to set the issue status to Resolved (or whatever status your configuration is setup to make issues read-only at). Would be nice to be able to mark individual issues read only without having to change their status. Having to change the status risks the issues not showing up when a reporter is searching for open issues like the one they are having (which is what helps to prevent duplicates in the first place).
5) Once issue X is closed, close all it's duplicates. I don't know of any way to do this in one step unless you can figure out a filtered view that will just show you those issues and then do a bulk change on them. I do think it would be nice if, when closing an issue that has duplicates, it would prompt you with the option to then close all issues marked as a duplicate of that issue. Or perhaps when viewing a closed issue, there could be a "Close Duplicates" button that would close all it's duplicates.
If issue Y is submitted and it is determined that it is a duplicate of issue X, I would:
1) Try and determine if there is any useful information in Y that is not in X.
1a) If so, try and integrate the new information from Y into X (through the additional information field, or a bugnote perhaps).
2) Create a relationship so Issue Y is a "duplicate of" Issue X (not the other way around).
3) Give Issue Y a resolution of "duplicate".
4) Make Issue Y read-only to prevent new information being added to it. Unfortunately, only way I know to do this is to set the issue status to Resolved (or whatever status your configuration is setup to make issues read-only at). Would be nice to be able to mark individual issues read only without having to change their status. Having to change the status risks the issues not showing up when a reporter is searching for open issues like the one they are having (which is what helps to prevent duplicates in the first place).
5) Once issue X is closed, close all it's duplicates. I don't know of any way to do this in one step unless you can figure out a filtered view that will just show you those issues and then do a bulk change on them. I do think it would be nice if, when closing an issue that has duplicates, it would prompt you with the option to then close all issues marked as a duplicate of that issue. Or perhaps when viewing a closed issue, there could be a "Close Duplicates" button that would close all it's duplicates.
-Joe
Mantis Version: 1.1.2
Disclaimer: Answers are based on the Mantis version above and may be inaccurate for newer/older versions which may have different configuration options and/or functionality.
Mantis Version: 1.1.2
Disclaimer: Answers are based on the Mantis version above and may be inaccurate for newer/older versions which may have different configuration options and/or functionality.
Re: Relationships clarification
jb_mantis wrote:[...]
I do think it would be nice if, when closing an issue that has duplicates, it would prompt you with the option to then close all issues marked as a duplicate of that issue. Or perhaps when viewing a closed issue, there could be a "Close Duplicates" button that would close all it's duplicates.
Great idea!
I'll love this feature in 1.2!
