It seems possible for an issue key to identify more than one issue simultaneously, and vice versa. In what circumstances is this possible and how can those circumstances be reproduced? I want to see this in action myself.
Two approaches I can offer:
For example, these API calls have signatures and implementations that indicate the premise is indeed possible, such as:
Also, what is best practice in handling such issues?
I ask in the context of an add-on developer targeting JIRA version 5.1 and newer + systems whose data has been upgraded from older versions where rules may have differed. This topic affects developer awareness, vendor's customer education & customer support activities, and JIRA plugin technicalities.
Yes, lots, almost every JIRA in the world is using "issue links". See https://confluence.atlassian.com/display/JIRA/Linking+Issues
Your reply serendipitously provides validation to my situation. But I chose the wrong wording -- sorry about that. Updated question.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.