How to automate Jira to create a issued based in a field of other issue?

[Paulo_Cerqueira]

Hi team, I hope you can help me on this apparently easy automation.

I have to create a series of automations for a upcoming project, this automations are set forth from the creation of an EPIC.

... When a Epic is created, based on the value of a field and the status of the epic some tasks/story are automatically created. This automation is done and working well.

The second stage of this automation that is confusing me.

Once a story (for example) is created; 1 or 2 subtasks are also created based on the value of a multi-select field on the Epic issue, which the story is linked to.


This is the requirement of one of many tasks that I'll have to create this similar automation;

I have set up a rule that creates both sub-tasks above, but when the field

--> [SDLC type] in the EPIC (parent) is selected [Config Change],

            --> The sub-task  "3 Amigos meeting" should NOT be created.

So far that is what I have created and it is working well. (meaning both sub-tasks are automatically created, but that should not always be the case)

I tried to create a rule based on IF/ELSE block, but nothing seems to be working.

I would love if you could help me as I have another 4 similar automations to do and this project is still in pilot stage. :-)

[Marc - Devoteam · Accepted solution]

Hi @Paulo_Cerqueira 

You will need to create a variable.

So when the Story is created, add a create variable action in the automation rule before creating the sub-task(s).

Name the variable and use the smart value {{issue.parent.SDLC type}} or {{issue.parent.SDLC type.name}}  to store the value of the SDLC type value of the Epic.

Then you could use IF/ELSE base the conditions on the variable being value x or y

[Paulo_Cerqueira]

HI @Marc - Devoteam 

Thanks for the explanation, it worked well after a few try, and it looks like that now;

 I first let the automation create all the regular subtasks I wanted and just then I add the condition. 

Much appreciated your support on this...

[Bill Sheboy]

Hi @Paulo_Cerqueira 

Given some known racetrack timing problems with the Work Item Created trigger, I recommend not using the new feature to add conditions to the trigger.  That can cause incorrect results for the condition tests.  Instead, use separate conditions.

And for your scenario, an additional condition is needed *before* that specific subtask is needed.

Assuming the subtask creation order does not matter, the rule could look like this:

• trigger: work item created
• action: re-fetch work item data 
• condition: type equals Story
• action: create the subtask for "requirement signoff"
• smart values condition:
  • first value: {{triggerIssue.parent.SDLC type.value.toLowerCase().join(",")}}
  • condition: does not contain
  • second value: config change
• action: create the subtask for "3 amigos meeting"

Please note well:

1. The above assumes the smart value for "SDLC type" matches what you show.  Please use this how-to article to confirm the correct smart value or custom field ID for the field.
2. I intentionally added the toLowerCase() function and used a lowercase comparison value to prevent accidental typos causing a mismatch in the condition.  You could instead remove that and confirm the condition checks the exact values for a match.
3. The above assumes the subtask order does not matter.  When it does, you could use if / else blocks or a branch to current work item for each subtask to ensure the rule does not stop processing at the first mismatched condition.

Kind regards,
Bill

[Paulo_Cerqueira]

Thanks  @Bill Sheboy for the reply, but the previous reply worked well.

Also your model is more complex, I'm not THAT savvy in Jira. :-)

Have a good day