The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

Jason Selby
Contributor
July 1, 2021

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

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Jack Brickey
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 1, 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?

Jason Selby
Contributor
July 1, 2021

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...

Jack Brickey
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 1, 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.

Jason Selby
Contributor
July 1, 2021

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

Jack Brickey
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 1, 2021

No. The old issue key will be gone.

Jack Brickey
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 1, 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.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events