Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

When transferring a project to the new ITSM template, will all the historic tickets be accessible?

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?)

1 answer

1 accepted

0 votes
Answer accepted
Jack Brickey Community Leader Jul 01, 2021

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. so will be Bulk Moving 'All Issues' when everything is replicated from one project to the other...

Jack Brickey Community Leader Jul 01, 2021

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.

Thanks Jack. So to confirm, i will be able to search on the original issue key ?

Jack Brickey Community Leader Jul 01, 2021

No. The old issue key will be gone.

Jack Brickey Community Leader Jul 01, 2021

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.

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events