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:
- Renaming an existing project (ID = 10005) key from ABC to DEF, and then creating a new project (ID = 10073) with (overlapping) project key ABC. Issue #1 from the former project #10005 is then identifiable with issue keys DEF-1 and ABC-1. Issue #1 in the latter, newly-created project #10073 is mapped to ABC-1. In this situation, ABC-1 refers simultaneously to two issues: issue #1 in project #10005, and another issue #1 in project #10073.
- Project keys are alphabet-wise identical, but actually differ by case. For example, there are two projects, with keys "xyz" and "XYZ". Using JIRA's Quick Search to search for "xyz-1" or "XYZ-1" returns both issues in either case, keyed by "XYZ-1" and "xyz-1".
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.
![Photo of Keiei Tanto [Vivid]](https://avatar-management--avatars.us-west-2.prod.public.atl-paas.net/557058:1aa21d9c-5e1b-43ac-99f6-088bd2b51ec8/a93b0373-6993-4973-a7c0-ed2ead034404/128)
