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

Migrating from old service template to new one

How many people have migrated from the old service template to the new one and what issues have you had? My major concern is being able to access old tickets and resources from the old template. Any information on your experiences would be much appreciated

1 comment

We migrated over to the new JSM template. We mostly started from scratch adopting the new workflows. Be careful with some of the fields you add to request forms. For example, I added the Affected Services field without realizing that it wasn't available for customers and they weren't able to raise requests. I only migrated the open issues in our queues from the old project to the new one. We decided to leave the old one in place for archival purposes. I wasn't planning on migrating those issues because we have a lot of other documents/resources and external systems that reference those issue keys. However, Atlassian creates a URL redirect from the old key to the new key if you move the issues to the new project. So it works pretty well.

I spent a lot of time configuring every little setting. If I did it again I would just notify our users of the change, use the default settings and just configure settings as needed. 

Like Jason Selby likes this

Thanks Patrick. That is really insightful, i am assuming that archiving the old project means that you can still access old tickets if necessary?

Yep. I didn't actually archive it, but rather adjusted the permission scheme so it doesn't appear on the customer portal. Admins and Service Desk Agents can still toggle to the project as needed. 

@Patrick Haley  - Hi Patrick, i cant find where i permission the customer portal, can you let me know where this is?


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events