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
Hi. We want to migrate from using change management in Jira software to Jira service management. What are des benefits to migrate? Particularly for change and release management? Pros and cons?
Hi @[deleted] , welcome to the community.
This is a tricky question to answer because it fully dependend on the complexity of your current change and release management configuration in Jira Software. Change and relase management setup in JSW can often be rather complex if it have continually improved over the years in an organization. Especially if you have buildt filters, dasboards, reports in Confluence, having manu users "on it", automation rules, etc.
The pros are many if you don't have any advanced setup in JSW. It comes "out of the box" and might suite your exact needs as-is or might need to be customized.
See this link for many pros and details.
The cons are only related to your current configuration, because starting from scratch there are no question about it; I would go for JSM and I see only benefits. Example of cons:
JSM is more or less aimed for operations and JSW is aimed towards developers (simplified). Earlier in server/DC versions this wasn't a so clear difference other than the portal itself, and it was named Jira Service Desk, hence many companies implemented their Change and Relase management processes into JSW.
Atlassian named it Jira Service Management because it is designed to support ITIL's definitition of service management. See attached link above regarding this.