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

Changing the status of a subtask

Martina

Hey all,

I am looking to make a rule that:

when a subtask #1 is marked as done, then change the status of the subtask #2 to to do.

The problem is that subtask #1 is the child of task #1, subtask #2 is the child of task #2 and these tasks (1 & 2) are linked.

I have been trying to pursue this by using this code, but it isn't working. I wonder if you have any suggestions. Thank you so much in advance!!

P.S. Apparently what isn't working is the smart values condition

Screenshot 2024-02-17 at 21.15.43.png

Accepted answers

All comments

Trudy P Claspill

Hello @Martina

What are the details in the Audit Log for the execution of this rule?

Where did you get the idea that this was a valid smart value?

How are tasks 1 and 2 linked? What type of link is used? Can task 1 have more than one other task linked to it using the same link relationship that is used for task 2?

This is a fairly complex indirect relationship that you are trying to follow. Have you considered instead creating a directly link between subtask 1 and subtask 2?

Do you have any third party apps that extend the capabilities of JQL, such as ScriptRunner Enhanced Search or JQL Search Extensions?

Martina

Hello Trudy,

Thank you so much for getting back!

1. Screenshot 2024-02-17 at 22.16.17.png

2. I invented it, I know the bold part works: {{triggerIssue.parent.LinkedIssues.key}}, I also tried: {{triggerIssue.parent.issuelinks.key}} but it doesn't work either.

3. Tasks 1 and 2 are associated using the normal link. Yes, task 1 can have more than one task similar to 2, linked to it.

4. How would you suggest making a direct relationship between subtask 1 and 2?

I haven't tried ScriptRunner, do you think it's possible this way?

Thanks!

Trudy P Claspill

1. Thank you.

2. You can't "invent" smart values. ;-) You can use only valid smart values. And what you have attempted to use is not valid. You can find more information about what are valid smart values for an issue type of object here:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/

3. Exactly which link type is used? Most Jira instances have multiple link relationships that might be used such as blocks/is-blocked-by, clones/is-cloned-by, etc. Can you provide a screen image of a sample Task #1 showing the Issue Links section and point out which of the linked issues would qualify as "Task #2"?

4. Depending on the type of Issue Links that have been created in your Jira instance you might use something that indicates a dependency such as depends-on/is-depended-on-by

subtask #1 is-depended-on-by subtask #2

subtask #2 depends-on subtask #1

If you have a direct link between the subtasks then it will be easier to construct the rule. Depending on being able to confirm the link between the parent issues makes the rule much more difficult. I don't know if it would be possible to construct the rule without the aid of an app that extends the JQL capabilities. I haven't had time to try to work through that scenario.

Martina

@Trudy P Claspill thanks!

How can I add a dependency between subtasks?

Task #1 is DPLY-324 while Task #2 is DPLY-346

Screenshot 2024-02-18 at 00.32.36.png

Thank you!

Rebekka Heilmann (viadee)

Hi @Martina

I would 100% second @Trudy P Claspill in the suggestions to simplify the relation between the Subtasks. Even after reading the thread I am still not 100% sure of how you're issues are connected and what you are trying to achieve from a business point of view.

Back to your current setup and automation rule, it would be helpful to get details of all steps to really understand what's going on.

The "for" branch looks weird. What are you trying to do here? Will that JQL always only return one issue? Are you not simply trying to get to the Issues parent or are you trying to get the other Subtask?

LookupIssues and LinkedIssues are Lists. If you are certain they contain only one issue in your case, you can access the first element (which will be of Type "Issue") by get(0) or "First" so accessing the first Element's key in LinkedIssues of the Triggerissue should look like:

Triggerissue.LinkedIssues.get(0).key or Triggerissue.LinkedIssues.First.key

Check out Jira smart values - lists | Cloud automation Cloud | Atlassian Support

Martina

Hey @Rebekka Heilmann _viadee_ ,

I have different tasks that have different flows, and different subtasks. The problem is that 2 subtasks (one from each task) are related. I wonder how would you add a dependency between these 2 subtasks?

A little bit more of context:

As I mentioned these 2 tasks have subtasks with different statuses: blocked, to do, in progress and done. Blocked means that the subtask is not ready to be done. Once a subtask (let's call it #1) from Task #1 is marked as done, this enables subtask (let's call it #2) from task #2 to be done, therefore, its status should be modified to 'to do'.

subtask #1 is the one in the first if function, and subtask #2 is the one in the for function. There will be more than 1 subtask #2 associated to that subtask #1 since there are more than one tasks #2 associated to only one task #1. I was trying to filter all of the subtasks (they contain that summary) that are associated to the subtask #1 that changed status. I mentioned 'blocked' too because this rule will change them from 'blocked' to 'to do'. Hopefully this isn't confusing.

Where are lists used? in the for command?

Thanks!

Rebekka Heilmann (viadee)

@Martina
Against all other advice (which still is, to link the Subtasks directly per "Blocks" Link Type - description provided by others) I managed to create a rule to achieve what you asked.

Assuming that what you said in the last comment is true 100% of the time:

1. Trigger and conditions need to be adjusted to your needs. TriggerIssue is the Subtask #1

2. Get the issues parent

3. Lookup the Linked Issue Task #2 -> they need to be linked by a specific LinkType. If you don't use the "is blocked by" you need to edit that part

4. Lookup the Subtasks of the first Issue (assuming this would always be Task #2)

5. Branch over all Subtasks (you need the "Related Issues" branch type, not the Advanced one)

6. transition the issues (or edit or do whatever)

Screenshot 2024-02-21 094009.png Screenshot 2024-02-21 094141.png

Again: Recommendation would be to link the Subtasks directly. You can reuse parts of the first Lookup for reference on how to get linked issues

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-work-management

jira-work-management-cloud