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; } } }

How to add a watcher to a sub-task in Jira Automation?

Leon Gumba

Hello!

I am creating a scheduled automation rule that creates a task in my project, and I need to create a sub-task for it right from the start. I want one of my colleagues to be added as a watcher, but only for that specific sub-task, not for the parent issue.

How can I achieve this? I can't create a nested branch (branch within another branch), and when I try to add a branch for sub-tasks, I get this error:

"This component may be incompatible. One of the following needs to be produced earlier in the rule by the trigger or with a 'for each' branch for this component to work: Issue."

Any idea how to work around this?

Screenshot 2024-10-28 134624.png

Accepted answers

Manoj Kumar Gangwar

Hi @Leon Gumba You can change the Branch by selecting the Children option or you can use the JQL option.

Doreen Undiri

@Leon Gumba using JQL option as Manoj mentioned Screenshot_20241028_174831_Samsung Internet.jpg

All comments

Manoj Kumar Gangwar

Hi @Leon Gumba You can change the Branch by selecting the Children option or you can use the JQL option.

Leon Gumba

Hi @Manoj Kumar Gangwar , and thank you for your response!

Unfortunately, the Children branch option also produces the same error.

Screenshot 2024-10-28 154214.png

However, the JQL branch option worked! I was able to find this topic and it was really helpful:

https://community.atlassian.com/t5/Automation-questions/Adding-watcher-to-subtasks/qaq-p/1939011

It is suggested to create variables before using JQL, which made the rule run smoothly.

Bill Sheboy

Hi @Leon Gumba

I believe there are at least four ways to do this with an automation rule:

With your current rule structure, add the Watchers by calling the REST API endpoint using the Send Web Request action, rather than with Manage Watchers
To create the sub-task, do not branch to the Most Recently Created Issue. Instead create the issue in the main rule path, setting the Parent field to {{createdIssue.key}} and then branch to Most Recently Created Issue (for the sub-task) to use Manage Watchers
Combining #1 and #2, add the Watchers with the REST API endpoint rather than branching
Using multiple rules, with the second one triggered by the issue create and checking the issue type (and other conditions) to decide when to add the Watchers