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
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
We are removing Jira service management in a few months. What kinds of things will it remove? For example, will it remove the Support issue type? Will service desk projects be unavailable?
If we need to set up a generic project to handle some of the functions, what do we need to be aware of if we are trying to reuse workflows, issue types, screens, etc. from the service desk project in the generic project?
Hello @Sigrid Schoepel
That is an incredibly broad question with thousands of possible answers.
I suggest you start by Googling 'Jira vs Jira Service Management' so that you get a rough idea of the scope of the differences.
Then Google 'Jira Service Management features' and read the product's main feature page, like this one, to see just how much will no longer available.
You may be better of hiring a specialist to do it for your company in a development / test environment first, then help with building the alternative functionality to try and replicate some of the lost functionality.