Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,560,407
Community Members
 
Community Events
185
Community Groups

Automation Help - Subtask in separate stories

Michael
Michael
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!
Get involved
Apr 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!!!

Answer
Watch
Like Be the first to like this
170 views

1 answer

1 vote
Bill Sheboy
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.
Get recognized
Apr 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,
Bill

Reply

Suggest an answer

Log in or Sign up to answer
Jira Software
Jira Software
TAGS
AUG Leaders

Atlassian Community Events

See all events