Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Prevent issue assignment based on field value

Mario P February 25, 2025

For HR I would like to implement an automation rule that prevents the issue being assigned to the same user that it is targeting.

Scenario:

User has complaint against HR employee that handles JSM tickets. If they make a ticket I would like to prevent this ticket to be assigned to that user(target) so that there is no conflict of interest.

What I tried:

When Issue is assigned

Compare if account ID is NOT the same as target account ID

Then set issue to Unassigned.

 

However I am having trouble with obtaining the information from a field called: Party name.

 

 

25-02-25__18-07-30-2178.png

2 answers

1 accepted

2 votes
Answer accepted
Mario P February 28, 2025

The logic didn't work out as expected in the example above so I reversed it and instead made and if statement to check for a field value.

Users can now "select" their agent instead of trying to "not assign because it's about the target"

I use the "manager" custom field to allow the users to select the 'agent' that can handle this case:

28-02-25__09-39-49-2184.png

If this field is empty, then we do not need to assign anyone specific so I can assign it to a user in a group. In this way you can use the manager field for request types that NEED to assign agents by the user.

For that we use the IF/Else statement:

28-02-25__09-43-33-2185.png

Now we have automatic assignment for users in this project space unless a user needs to assign an agent themselves.

1 vote
Mikael Sandberg
Community Champion
February 25, 2025

Is the field Party Name a user type field? And does it have the space in the name or not? If it has a space you have to use the space in the smart value as well or use the customfield_xxxxx instead.

Mario P February 26, 2025

Goodmorning,

Good questions.

The field looks like this:

27-02-25__08-36-42-2180.png

 

And judging by the Aa indication it is probably a user type field:

27-02-25__08-38-46-2181.png

Instead of naming it I could identify it with it's custom field ID? That's probably in Issues > Custom fields > Field name > edit details > copy id from URL correct?

On another note, is the logic sound? To leave it unassigned might not be preffered I would rather assign it to someone except the for the target.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events