I'm trying to do the following
When I create a new version I want to define a few standard tasks in that release.
I added a new automation rul that triggers when a version is created. this automation creates a new task, but in the task i can not figure out how to place the fix version of the newly created version that triggered the automation to the task.
What can I do to capture the last created fix version?
Hi @Adriaan Peeters -- Welcome to the Atlassian Community!
For triggers like Version Created, the smart value {{version.name}} contains the triggering one.
When you use the action to create issue, select Choose Fields to Set, and select Fix Version. Then type in {{version.name}} and when prompted to use the smart value, select it.
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bill Sheboy
I have followed the above steps and it doesn't seem to be working. Am I perhaps missing anything? This is my automation rule:
The rule returns successful but the Fix Version field on the newly created card is still empty:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jacey Romon
Interesting...I retested and this worked for me in a free license, company-managed project.
Please try to select the specific project in the Create Issue action to rule some things out.
Also, some questions...
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bill Sheboy
Thanks very much for the response.
I have now narrowed down the rule to create the issue in a specific project. The issue is created but the fix version is still not populated. Please see below.
To answer your questions:
I appreciate the help!
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.
Hi @Jacey Romon
I'm sorry for the delay in responding as I was out-of-office for a while.
Thanks for the information about your rule's scope as global; that is likely the cause of this symptom...
The way to confirm this is to look in the "iTest (IT)" project to see if the version exists. I suspect it does not.
One possible fix is to create the new version in that project when needed with a rule action before creating the issue. I believe that will raise an error in the audit log if the version already exists, and still continue processing for the assignment.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bill Sheboy
Thanks very much for the response.
I have managed to figure out a workaround that we will use instead of trying to automatically populate the fix version.
Kind regards,
Jacey Romon
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.