Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

History and Subtask - Priority

hi, guys!

A question: Is it possible to make the subtask's priority follow a history's priority?

For example: my history has 2 subtasks, and the history's priority changed for highest and I want that my subtasks' priority changes for highest too but automatically. 




2 answers

1 accepted

1 vote
Answer accepted

Hi @Louise de Melo Macedo -- Welcome to the Atlassian Community!

To confirm your use case, when a user story's priority changes, you want the priority of its subtasks to also change.  Is that correct?  

If so, you can do that with a rule such as:

  • trigger: field change for priority
  • condition: issue type is Story
  • branch: on sub-tasks
    • action: edit issue to set the priority, copying it from the parent

Please look at this documentation and examples to learn more about automation rules:

Best regards,

@Bill Sheboy 

Thanks a lot!! Your answer helped me!!

Like Bill Sheboy likes this

This rule works when the field is edited, but I would like it to trigger on creation of the Story to copy the Story's priority down to the sub-tasks.

When i change the trigger to: Issue Created > Issue Type = Story > For Sub-Tasks > Copy Priority from Parent, this rule fails. It seems to run between the sub-tasks getting created, is this why it is failing? Is there a way to have it run in an order that would work? 

Hi @Marrianna Martinez -- Welcome to the Atlassian Community!

Automation rules and timing with Jira events can be challenging to reconcile.  Would you please post an image of your rule, as that will provide some context.  Thanks!

Until then...How are you creating sub-tasks?  Normally the issue is created and then its sub-tasks can be added.  If you are trying to trigger on the story creation, the sub-tasks probably do not exist yet.

So you can reverse this, and let the sub-tasks drive the action as you know the story exists by that point;

  • trigger: issue created
  • condition: issue type equals sub-task
  • action: edit issue to copy the priority from the parent issue

This will fire as each sub-task is created.  To keep things in sync, you also need a rule triggered on change of priority for the parent story, and then copy that down to the existing sub-tasks.

Kind regards,

Hi Bill, I created the rule you mentioned and it was failing, but I made a few changes to other rules I have set up in the project and I'm not sure what caused it, but the rule is working now.



Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Do you use Jira Cloud with Microsoft Teams?

Hi, Jira users! Do you use Jira alongside Microsoft Teams? We want to hear how you’ve used the power of Jira Cloud and Microsoft Teams (via the Jira Cloud for Microsoft Teams app) to achieve a team...

533 views 1 10
Read article

Community Events

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

Events near you