Need inputs on the below use case,
JIRA workflow - When the development is completed for a bug and assigned to QA for testing, We have an automation rule to create tasks by cloning the original ticket to port the code fixes to all the supported releases ( 3 releases )
I am cloning the original issue with the automation rule to create sub-tasks , Need input on assigning fix version for the sub-tasks
Porting sub-tasks are created for atleast 3 releases ( Summer, Winter and Spring )
If the original fix is done in Spring20 release then porting ticket will be created for Summer20,Winter20 and Spring 21 releases
If the original ticket's fix version is SP20.01.15 ( Spring 20 , 15th Jan ) then the cloned tickets fix version should be the next version in the appropriate release
Summer 20 Task - SU20.01.29 ( Summer20 , 29th Jan )
Winter 20 Task - WI20.01.29 ( Winter 20, 29th Jan )
Sample Fix Versions,
Summer - SU20.01.15, SU20.01.29, SU20.02.12, etc.,
Winter - WI20.01.15,WI20.01.29,WI20.02.12 ,etc.,
All these fix versions are available in the "Versions" dropdown
What are the ways of solving this use case ? Do we have an option to write some code logic to extract the fix version , manipulate and assign it as part of the clone issue ( above screenshot ) work flow ?
Any help/pointer is appreciated
For code logic, you can take a look at the Automation Conditions - you can use Advanced compare condition and an IF-ELSE loop.
For assigning the Fix Version, this might be tricky. It looks like there are smart values for Fix Version; Smart values - lists - you will need to iterate over the list and choose the value that you want for each IF-ELSE condition.
I hope this helps.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events