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

[Ivan Andrieiev]

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.

[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

[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]

@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]

[Ivan Andrieiev]

[Niklas Maier _KUMAVISION AG_]

Hey Ivan,

you have to use Branch flow / related work Items and catch the JQL Option

here a detailed picture of the Branch Config:

the Branch is created to perform the Transition Action on all Work Items which follows the Branch Filter specified with JQL, which in your case, are all Issues assigned to the current assignee, in the Status "in Progress" and don't have the same issue Key like the one triggered the Automation. 

if you want to learn more about branching and it capabilities, I kindly suggest this Atlassian Documentation: https://support.atlassian.com/cloud-automation/docs/jira-automation-branches/