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

Trigger for Linked Tasks

Mahesh Ghanta

I have a JIRA Project with Type Team-managed business. I have created Task_1 and Task_2. I had set up Task_2 as blocked by Task_1. Goal I am trying to achieve is, I should not be able to Close (change status to Done) on Task_2 as long as Task_1 is Open (Status should not be Done).

So to implement that, I have used Automation Trigger. I am attaching a screenshot for the Trigger I have written. After implementing this trigger I am able to close Task_2 with Task_1 still being open. Can you please let me know if I am making any mistake here.

Trigger for Blocked Task.JPG

Accepted answers

Bill Sheboy

Hi @Mahesh Ghanta -- Welcome to the Atlassian Community!

The image you posted seems to be truncated. Please post an image of your complete rule and another image showing the audit log details for the rule execution.

Until we see those...

Please note links have direction (e.g., "blocks" versus "is blocked by"), so ensure you are checking the correct direction to find the work items with the lookup's JQL expression.

Another thing to check: are all of the linked work items in one single project? When they are in multiple projects, the rule scope in the details at the top of the rule must be "multiple-project" or "global" in scope. If you need this, please discuss this rule with your Jira Product Admin to understand the impact to other projects and to make the changes.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Mahesh Ghanta -- Welcome to the Atlassian Community!

The image you posted seems to be truncated. Please post an image of your complete rule and another image showing the audit log details for the rule execution.

Until we see those...

Please note links have direction (e.g., "blocks" versus "is blocked by"), so ensure you are checking the correct direction to find the work items with the lookup's JQL expression.

Kind regards,
Bill

Varsha Joshi

Hi @Mahesh Ghanta

Welcome to the community!

One way to accomplish this in the workflow in the transition set up. Click on the transition and add rules on the right column and select Restrict based on the status of the subtasks.

Hope this helps.

Mahesh Ghanta

Thank you @Bill Sheboy

I have attached 3 screenshots. One is for the Rule and the other 2 are for Audits. I am positive I am using Task_2 is blocked by Task_1, and I can successfully close Task_2 without the dependency on Task_1 status. Both these are tasks are under the same project.

Trigger for Blocked Task.JPG

Mahesh Ghanta

Hi @Varsha Joshi

Thank you. I also have that Restrict based on status of the subtasks enabled, it only lets Parent Tasks not to move forward to Completion (Status Done) when its Sub-Tasks are not completed yet.

This rule is not working for 2 tasks having linked dependency.

Bill Sheboy

Let's make two changes to your rule and then re-test it:

The new feature to add conditions to triggers conceals why a rule did not trigger. Until Atlassian solves that and other limitations with this feature, I recommend not adding conditions to triggers. Instead, add a separate condition after the trigger.
Your rule uses the Field Value Changed trigger on Status. However, there is a separate trigger for Work Item Transitioned because that is a different event type. Please change your rule to use the different trigger.

After both of those changes, please re-test your rule. Thanks!

Mahesh Ghanta

Thank you @Bill Sheboy I have made one change to my Worflow and it started working. Earlier I had my workflow transitioning only from In Progress to Done, now I have also enabled the Transition from Done to In Progress and the Trigger started working fine. I have attached sample screenshot for the Workflow. Jira Workflow.JPG

Appreciate all the help you have provided here.

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-cloud