Hello all,
I have releases set up for the whole year and use the following alpha-numeric naming convention for them: "Release 2022.01", "Release 2022.02" and so on....
I am looking to automatically set the fixVersion to the appropriate release, when a 'Due Date' is populated or updated.
Is there a way to do this using JIRA automation? Thank you very much in advance for any and all help.
Cheers!
HI Dinesh,
I do not think you can search for a fix version within the due date range and set that fix version via Automations. ( If that is what you intent to do)
You could probably have a if else statement that say if date range in this then set fix version to say 2.1 . however this will need you to update whenever you add or edit a new fix version.
You can look at using scripts and API;s to achieve this functionality.
Thanks
Hi @Aradhana Gupta ,
Thanks for taking the time to respond. To clarify, I have already set up the release versions for the year which are available for selection on a ticket's fixVersion field. The idea is that when my team updates a due date on any ticket, I want the fixversion to be set to the same month's release as the due date.
I found a smart code formula somewhere but it does not seem to be working.
I have attached a few screenshots of what I have now.
Thanks again!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Create variable action might help in this case.
You can use it to create a variable called version with value: BWAP {{issue.duedate.getYear()}}.{{issue.duedate.getMonthOfYear()}}
Then in the Edit issue action, you can set the fix versions field with {{version}} (the variable you created).
Hope that helps.
Eric
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.