A customer uses baselines quite a lot. They want to create an issue, Issue_001, then
clone Issue_001, creating Issue_002 - representing baseline 002.
Clone Issue_002, creating Issue_003 - representing baseline 003.
Clone Issue_003, creating Clone_004 - representing Baseline 004.
and so on.
They would like to have a field in each of these issues, a sort of universal ID, that would refer back to the original issue - Issue_001.
I was thinking they could do this by using the IssueID.
Whey would like to have this done automatically.
What do you think? Is using the IssueID a good idea? Can this be done automatically evey time a clone is created - get the IssueID and populate a field with it? Is there a better way to do this?
Thank you for your help,
Jim
Hi James,
Cloning an issue should automatically create a link between the two issues. It should be in the Linked Issues field. And/or you could also create a custom field and copy the key from the original issue into the custom field of the second issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.