Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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.

Atlassian Community about banner
4,466,761
Community Members
 
Community Events
176
Community Groups

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. 

 

 

thanks!

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

@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,
Bill

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.

Thanks!

Marrianna 

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events