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

Releases/Versions in jira service management

We previously used releases/versions in a jira software project to record what tickets and developments had gone into what release - and to create the release notes.


I'd like to do the same with tickets in jira service management - I can see that I can create a version under project settings in jira service management and set the fix version, but I can't get release notes out in the same way as a project.


Is there a way to enable this for jira service management? 


I also need to include tickets from multiple projects (eg the support project and the software project) in a release - I don't know if there is a way to make versions available across multiple projects?

1 answer

1 accepted

1 vote
Answer accepted
Brant Schroeder Community Leader Dec 01, 2022

@Nick Lucey To have full functionality you will need to use a software project.  We created linked issues from our service desk project to our software project to properly control and report on releases.  We used automation to do this and keep everything in sync.  You can learn more here: 

That's a shame that you can't do it in service management - the main reason for implementing was to reduce duplication across other systems and minimise confusion for our support teams of having information in multiple places. 

I'll continue looking for another way of doing this, but thanks for your answer. 

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events