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

Automation Assign Issue transition to someone who wasn't just working on it

Adrienne Van Halem

I would like to create an Automation:

When: Issue transitioned from In Progress to Ready for Review
Assign issue to A user in a defined list, Round-Robin
User list: X, Y, Z

But not the person who just did the last task.

Documents are being written and it needs to be assigned to someone new for review. ie. X,Y and Z are all on the list of people who can be assigned to, but X did the document writing, so Y or Z should review it.

Any way to add this rule? like a NOT {{assigned to}} limiter?

Thank you!

Accepted answers

Adrienne Van Halem

@Bill Sheboy @Mark Segall Using 'Balanced workload' I've attempted to put

assignee != currentassignee

into 'JQL to restrict issues'.

I'm not sure if this will work as intended. It's allowed me to list users to choose from, does this function limit the selection of the assignee to be NOT the current assignee?

Small team. 3 people the flow could go to. 6 people who could be 'current assignee'

All comments

Mark Segall

Hi @Adrienne Van Halem and welcome to the community!

The round robin could get quite complex. How many people are on the team?

Bill Sheboy

Hi @Adrienne Van Halem -- Welcome to the Atlassian Community!

I do not think that is easily supported with out-of-the box features of automation rules. I suggest trying team or self-assignment instead.

More on your specific use case...

I just did a quick test and confirmed I was not able to do this with a created variable list of users. (The problem is the list function get() cannot take a variable as a parameter; if it did this would be possible by generating a random number to pick the next person.)

An elaborate work-around would be to create a Jira user group specifically for this assignment, replace the members with the REST API function to not include the current assignee, and then use the built-in random assignment.

Kind regards,
Bill

Adrienne Van Halem

@Bill Sheboy @Mark Segall Using 'Balanced workload' I've attempted to put

assignee != currentassignee

into 'JQL to restrict issues'.

I'm not sure if this will work as intended. It's allowed me to list users to choose from, does this function limit the selection of the assignee to be NOT the current assignee?

Small team. 3 people the flow could go to. 6 people who could be 'current assignee'

Bill Sheboy

When using balanced workload with that JQL statement, the rule editor states that:

The issue will be assigned to the user with the least amount of open issues assigned to them as defined by the jql. If multiple users have the same count, one will be randomly selected. For project scoped rules, only issues in that project will be counted.

So...I interpret that statement means if your JQL excludes the current user assigned from issues then the current user is more likely to be selected: they will have a zero number of issues returned by the JQL.

Simmo_9kntn7

That's right, the JQL is intended to help balance the load not filter out

Adrienne Van Halem

I was attempting to do it via Smart Value but I'm struggling with the syntax (not a coder). Would it be possible to do that way?

Welcome!

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

Quick Links

Find more posts tagged with

automation

assign