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.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs