Automation Help - Subtask in separate stories

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 14, 2023

Having some issues creating two automations.. Tried to build them for ours but cant figure it out. Tried to use branching but having a hard time finding a way to get the automation to move out of the subtask, out of the story, into a different story (in the same epic), and into the subtask. 


Here's the structure of the Epic/Story/Subtask

  • Epic Name
  • Story 1
    • Subtask 1
  • Story 2
    • Subtask 2


First Automation Goal:

  1. Trigger: when subtask 1 is created
  2. If "Subtask 1" description is "Low", then change "Subtask 2" description to "ABC" and mark workflow status of as done.


Second Automation Goal:

  1. Trigger: when subtask 1 is created
  2. Change the epic priority to match the description of "Subtask 1" (we only put "low" "Medium", and "High" in the description)


Any help would be very appreciative!!!

1 answer

1 vote
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 15, 2023

Hi @Michael -- Welcome to the Automation Community!

First thing: when posting questions about automation rules, please post images of your complete rule and the audit log details showing the rule execution.  Those will provide context for the community to offer suggestions.  (As a tip for longer rules, try using a browser addon or screen capture tool so the entire rule shows in one image.)

Until we see that information...

Next thing: this seems a complicated scenario to me.  What problem are you trying to solve with your automation goals?  Understanding that may reveal a different approach than what you have described.

Next, are you certain you will only every have 2 stories in the epic?

If so...for your first goal you might be able to:

  • use the subtask's parent field to find the story,
  • which will then indicate the epic,
  • which will identify the other story, and
  • so it's subtask.

I am using Jira Cloud and not Jira Server, so I cannot test if this would work.  One reason it might not work is the related/linked issues in Jira do not apparently store all fields.  If they did, a single smart value expression could pull in many issues.

Kind regards,

Suggest an answer

Log in or Sign up to answer