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.
We use the Releases feature, but manually create each release. They are always on the same day each week.
We create a few in advance, so if issues are destined for the week after next, they can be tagged as such.
For example, right now we have:
Thanks to this forum, we currently have an automation that releases the version when all the issues tagged to it are marked as Released.
We now need a trigger for when a version is released, it creates a new one 4 weeks in advance, e.g.
230509-ProductName is Released
230606-ProductName is created.
I suspect we will have to change our versions from date numbers, to 0001,0002,0003 etc, but what is possible and best practice?
First thing, and IMHO, there are no best practices...only better and worse ones for your team.
That being noted, if your team finds it helpful to create the versions with some form of the date included, you can do that using the Create Version action and the date time functions of rules, particularly the format() function: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/
Without seeing your complete rule, I suspect you can just add the needed actions to create the versions, and increment/format the date to build the version name. One wrinkle is deciding if you want to detect if the version is already created (and so not try again) or just do it, and ignore the errors; both are possible with the rule you describe.
Give it a try, and please let the community know how that works for you. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.