Hello Atlassian Community,
I need your help regarding a peculiar issue raised by one of our Jira software users and it's my first time encountering it.
User says that he can't find the issues he created in the Jira project and user needs these issues to be linked to a parent Epic. Upon checking, sample issue EET-676, searching for it in "search all issues" it returns a different issue key and number: EBT-19.
Further checking EBT-19 in the "History" tab under "Activity" it shows "User Updated The Key".
I need help from the community to explain how the user was able to "Updated the Key" given that he is not a Jira administrator? How did the user, or what were the steps in updating the key? And can it be return back to the original key, in this sample back to EET-676?
Your feedback and help is highly appreciated.
Hi @Ikem Abellon
I See that the Key is Changed from EET-676 to EBT-19. Is there any chance where the issue is moved to another project. I recommend you to check the project in which the issue/ticket is present currently.
Note:- When the issue is moved from one project to another the Key of issue updates according to the new project.
Yes, exactly this.
When an issue is moved from one project to another it gets a new issue key comprised of the destination project's key and the next sequential number in that project.
You can still search for the issue based on its original issue key because Jira keeps track of such issue moves exactly for the purpose of helping you find the issue after it has been moved when all you have is the original issue key.
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.