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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Looking for some feedback/thoughts on this. Currently we are pretty traditional in that we : add issues to versions, manually deploy the issues in the version and then release said version when every issue is closed and deployed.
The lightening talks for the new JSM features show lots of cool automations between jira, bitbucket and JSM. I’m wondering how versions play into this ? Can a version creation be automated along with the inclusion of issues and release of the version or is it better to have issues already in a version in jira and just close it after all issues are closed? Any thoughts on how jira versions and automating deployments would be appreciated.