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

Limit "In Progress" tasks to one per specialist; move others to "On Hold"

Ivan Andrieiev_oq43e6

I need to set up automation so that each specialist has only one task in one status (in our case, In Progress). The remaining tasks should be transferred to another status (On hold). That is, the flow looks like this: the worker takes on another task, and the previous one is transferred to the On Hold status.

Accepted answers

Niklas Maier _KUMAVISION AG_

Hey Ivan,

this looks like a perfect fit for a Branch Rule.

Automation Summary:

Trigger: Work item transitioned to "In Arbeit (In Progress)"

Branch: For JQL — find all OTHER tasks of the same assignee that are currently "In Progress":

assignee = {{issue.assignee.accountId}} AND status = "In Progress" AND key != {{issue.key}}

Action: Transition the work item to "On Hold"

Keep in Mind, that the Automation needs to have Permission in the Workflow to transition the issues from "In Progress" to "On Hold".

More Information about branching:

https://support.atlassian.com/cloud-automation/docs/jira-automation-branches/

I hope this Answer will help you to build the perfect Solution for your Team!

Best Regards
Niklas

Bill Sheboy

Hi @Ivan Andrieiev

There are risks when using an automation rule to limit work in progress (WIP) by moving items to another status...such as unintended consequences.

For example, people may decide to not update Jira and continue working on other items regardless of status selected; then the board no long reflects reality. And, people may be less likely to focus on why they cannot continue on the current item in progress, perhaps due to impediments. Eventually, the WIP limit and flow measures the team uses become less helpful.

As an alternative, consider doing a root cause discussion with the team on "why are people trying to move multiple tasks to in progress?" This analysis may lead to other actions to try, focusing on the source of the problem.

Kind regards,
Bill

All comments

Niklas Maier _KUMAVISION AG_

Hey Ivan,

this looks like a perfect fit for a Branch Rule.

Automation Summary:

Trigger: Work item transitioned to "In Arbeit (In Progress)"

Branch: For JQL — find all OTHER tasks of the same assignee that are currently "In Progress":

assignee = {{issue.assignee.accountId}} AND status = "In Progress" AND key != {{issue.key}}

Action: Transition the work item to "On Hold"

Keep in Mind, that the Automation needs to have Permission in the Workflow to transition the issues from "In Progress" to "On Hold".

More Information about branching:

https://support.atlassian.com/cloud-automation/docs/jira-automation-branches/

I hope this Answer will help you to build the perfect Solution for your Team!

Best Regards
Niklas

Niklas Maier _KUMAVISION AG_

the automation in Jira:

Ivan Andrieiev_oq43e6

@Niklas Maier _KUMAVISION AG_ Hello, thanks for your help, I have a few questions. Please help me
What kind of branch I have to choose? And why this group was created?

Ivan Andrieiev_oq43e6

Screenshot 2026-06-16 at 11.24.29.png

Bill Sheboy

Hi @Ivan Andrieiev

There are risks when using an automation rule to limit work in progress (WIP) by moving items to another status...such as unintended consequences.

Kind regards,
Bill

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