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.
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.
1 answer
HI @GBE ,
I hope someone else will jump in with additional tips, but first thing is that you can bulk update issues, for example moving them from a Software to a Jira Service Management project, in order to keep the existing issue history.
I'm going to assume that you mean you've been using a Jira Software project with limited scope, and that now you want to set up a JSM project. It's important to understand the differences in how a Jira Software project works compared to a Service Management project. For example, JSM projects have request types, queues, and SLAs and Software projects do not. I don't see a way around avoiding having to do some configuration for your request types and portal set up. There are a lot of templates available now, so you can get started with something that already has request types, workflows, and basic queues.
Here is a discussion to better understand the differences between the two types of projects:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.