nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Update sub-task's field of same parent issue if action occurs on other sub-task

Riccardo_l7zpgd

Hey everyone!

This is my first request to the Community, so I am really excited to contribute to this whole knowledge-sharing experience.

I am trying to implement 2 automations in one of the projects I am coordinating.

Important disclaimer: in this project, each new user story is created with 3 sub-tasks by default. Those are always named "BE", "FE", "Validation".

I would like to:

- If both "FE" and "Validation" subtasks are both in To-Do, when the "FE" subtask is assigned to user X, I want "Validation" of the same parent issue (user-story) to be assigned to the same person.

- When "BE" sub-task is moved to Done, I would like to post an automated comment on the "Validation" subtask of the same parent issue tagging the assignee of the latter.

For the second one I have already made an attempt, but I am not sure.

What I am most uncertain of is how to render in JQL language the condition "subtask of the same parent issue".

I tried to do it in this way (see attached). Thanks to everyone that would help! Screenshot 2022-12-07 at 15.44.44.png

Accepted answers

Mark Segall

Hi @Riccardo and welcome to the community!

Your second rule looks correct. Are you finding any issues with it?

For the first rule, you'd need something like this:

TRIGGER: Field Value Changed (Assignee)
Note - I use Field Value Changed instead of Issue Assigned because it ensures that if someone removes the assignee it will sync that up too.
CONDITION: Summary Contains FE
BRANCH (JQL):
- Summary ~ "Validation" AND parent = {{issue.parent}}
- ACTION: Assign Issue (Copy from Trigger Issue)

All comments

Mark Segall

Hi @Riccardo and welcome to the community!

Your second rule looks correct. Are you finding any issues with it?

For the first rule, you'd need something like this:

TRIGGER: Field Value Changed (Assignee)
Note - I use Field Value Changed instead of Issue Assigned because it ensures that if someone removes the assignee it will sync that up too.
CONDITION: Summary Contains FE
BRANCH (JQL):
- Summary ~ "Validation" AND parent = {{issue.parent}}
- ACTION: Assign Issue (Copy from Trigger Issue)

Riccardo_l7zpgd

Hey @Mark Segall, thanks so much for getting back to me so quickly.

Something unexpected happened to the second rule, but only once and it's now difficult to get back to it but I will keep a close eye and let you know if you want!

Thanks so much for the tips on the first rule, it worked but with one small change in the JQL query that rules the branch relation

BRANCH (JQL):
- Summary ~ "Validation" AND parent = {{issue.parent.key}}
- ACTION: Assign Issue (Copy from Trigger Issue)

Thanks again!

Mark Segall

Interesting - Usually adding .key is redundant. Thanks for sharing that and happy this is working for you. 🙂

Please share the audit log if you happen to see the rule fail again and need some further assistance.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud