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
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.
In a classic project, I could create release notes easily when I marked a version as released. Is there a similar mechanism for a next-gen project?
Hi @kenk
not at the moment, unfortunately. Next-gen Release hub doesn't allow you to see the Release detail like in Classic projects.
There are some improvements coming this year to the release hub so I would expect some changes coming soon but can see the release notes listed there yet.
Link to the Next-gen roadmap ✨ https://www.atlassian.com/software/jira/whats-new/next-gen#intheworks
But maybe you could just use JQL to filter for issues in this release and then export them as a list as a workaround for now (there are several options for export in search)
If that's something that blocks you a lot we have a planning plugin that will allow you to generate them 👉 https://marketplace.atlassian.com/apps/1219470/swanly-release-roadmap-timeline-for-jira
Hi @Nikki Zavadska _Appfire_ ,
Thanks for the reply. It's a hassle to do it by hand (this is one of those jobs truly made for automation) but if that's all there is, I'll have to go with it. I'll take a look at the plug in.
Cheers,
Ken
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @kenk ,
I would recommend you one more plugin which can help you to generate Release Notes: Release management for Jira.
In the add on you can
1. Create rich text multiple templates for release notes.
2. Add variables from version or general context. Such as, starter, release dates, author of the release notes etc
3. Inject SQL based dynamic tables which can represent certain set of issues in the version
Hope it will help you,
Yuri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.