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

Help with automation

Sara

Hello, I have an automation to transition tickets to the status blocked if the linked issues, is blocked by, has not been transitioned in the last 7 days. The automation is scheduled to run every day, and works fine but instead of transition the original ticket try to transition the linked ones, can you please help me? Thanks

Captura de pantalla 2026-06-03 a las 13.49.59.png

Accepted answers

C_Faysal _CFcon_

Hi @Sara

The cause is the branch. Everything, including the Transition action, is sitting inside the "For: Linked work items / is blocked by" branch. Inside a branch, {{issue}} no longer refers to the work item that triggered the rule, it refers to the branched (linked) item.

Straight from Atlassian's docs: "All actions and references to {{issue}} will point to the related work item, not the trigger work item."

That's exactly why your rule transitions the blockers instead of the original ticket.

regards

All comments

C_Faysal _CFcon_

Straight from Atlassian's docs: "All actions and references to {{issue}} will point to the related work item, not the trigger work item."

That's exactly why your rule transitions the blockers instead of the original ticket.

regards

Shalini Pradhan

Hello @Sara ,

Good day! Welcome to Atlassian community

As @C_Faysal _CFcon_ mentioned, its happening because of the branch. Your branch is set to "For: Linked work items -> Types: is blocked by", which means everything inside that branch executes in the context of the linked issues, not the original (trigger) issue. Since your "Transition work item to BLOCKED" action is inside this branch, it's transitioning the linked issues instead of the original ticket.

Move the "Transition work item to BLOCKED" action outside and below the branch, so it executes on the original trigger issue.

Sara

Thank you! how can I add the transition outside the branch but still apply to every ticket in the JQL of the scheduled? Not sure how to manage this

Sara

Thanks, I realized the issue is that, but not sure how to manage so applies to all issues in the JQL if IU set the action outside the branch

C_Faysal _CFcon_

From what i understand from your screenshot and the expected result it looks like you don't need a branch at all @Sara

try this instead:

here is the conditional part:

One note on the 7-day check:

NOT status CHANGED AFTER -7d catches any status transition. Your original statuscategorychangeddate only updates when a work item moves between status categories (To Do / In Progress / Done), so a blocker bouncing within the same category would still look "stale." If that distinction doesn't matter for you, either works.

Hope that helps!

Sara

that works! thank you so much. More easier than expected

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