You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I am in the middle of transferring to the new ITSM template from the standard Service Template withing Jira Service Management. Will all historic tickets be accessible for audits and what will happen to the original project key (reference number?)
I guess that depends on how you are “transferring” The issues from one project to another. Are you simply using the move function or something else?
I am following these instructions. https://support.atlassian.com/jira-service-management-cloud/docs/can-i-move-my-existing-project-to-the-new-itsm-template/ so will be Bulk Moving 'All Issues' when everything is replicated from one project to the other...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yep that is the “move” approach. If you follow that process then yes you should preserve all issues as part of the move. Note that your issue keys will be different but all tickets should exist.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Jack. So to confirm, i will be able to search on 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.
You might consider creating a custom field (OldKey) and run an automation to copy the issue key into that field then ensure the new project retains that custom field. I have not done this but should work.
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.