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 set up, only current assignee can change assignee

Eveline de Peffer

Hello,

I would like to set up automation that only the assignee can change the assignee to someone else.

I have used the Field value changed. When value changes for assignee with the smart values: {{initiator.accountId}} does not equal {{issue.assignee.accountId}}.

Then edit work item, Edit work item fields, Assignee {{issue.assignee.accountId}}

Which should revert the assignee back to the original assignee. But it doesn't seem to work.

Any ideas what I could be doing wrong?

Accepted answers

Eveline de Peffer

Thank you all for the help. With the Jira permission scheme it's possible to limit that only the current assignee can reassign issues. This only prevents unassigned issues from being able to be picked up by the team. For us it was not feasible to have them assigned to one person who reassigns them due to the amount of issues we receive.

With automation I've been able to set up the following, to make sure only the assignee can reassign issues and unassigned issues can be picked up:

Schermafbeelding 2025-07-30 112437.png

All comments

Ana Livia Rocha Silva

Hi @Eveline de Peffer, welcome to the Atlassian community!

Instead of using automation, have you tried achieving this using the Jira permission scheme? You could try granting the assign issues permission only to the Current assignee and the automation user (assuming the first assignee is set by an automation).

Hope I was able to help.

Kind regards,

Ana

Liz Tanner

Hi there @Eveline de Peffer, Welcome to the Community! I have a couple of answers for you and a couple of possible solutions too.

1st Issue Inhibiting Your Automation:

Automations cannot designate user-level role permissions. This is better suited to permission schemas (user or group permissions, e.g.)_and workflow conditions/restrictions.

2nd Issue Inhibiting the Automation:

Your automation rule uses Smart Value {{issue.assignee.accountId}} correctly on the first Assignee change. On the reversion though, the Smart Value {{issue.assignee.accountId}} now holds the account ID for the Assignee that is reverting back to the original Assignee.

Since the rule is comparing the Second Assignee's account ID to the original Assignee's account ID, the rule fails.

Potential solution:

Configure the Assign issues permission in the project permission scheme.

If you still need an automation to revert to the original Assignee once the new Assignee finishes something, that'll be a really easy breezy workflow to top it all off. But, I want to make sure that is still what you need before sending more info; this is a lot i know!

Eveline de Peffer

Hello @Liz Tanner,

Thank you for the information. Using the project permission scheme might be the best option.

Where can I find the project permission scheme? Could it be I need more admin permissions?
These are the setting options I have access to.

Schermafbeelding 2025-07-23 171554.png

Eveline de Peffer

Hello @Ana Livia Rocha Silva

Thank you for the information. Where can I find the Jira permission scheme?

Kind regards, Eveline

Ana Livia Rocha Silva

Hi @Eveline de Peffer!

You can find it in the project settings, in Project permissions:

Kind regards,

Ana

Eveline de Peffer

Hello @Ana Livia Rocha Silva

That does work. Only problem now is it also restricts unassigned issues. Is there a work around for that?

Kind regards,

Eveline

Eveline de Peffer

Hello, @Liz Tanner ,

I've also noticed that when I use the permission scheme to change it to the current assignee, unassigned issues can also not be picked up by users.

Do you have an idea how it could work, that someone can assign unassigned issues to themselves but not if they have already been assigned to someone?

Kind regards,

Eveline

Pedro Olmo_7tm5vp

Hello @Eveline de Peffer ,

You should configure the Assign issues permission in the project permission scheme.

With this permission, you can limit who can assign a ticket to a project.

Regards

Eveline de Peffer

With automation I've been able to set up the following, to make sure only the assignee can reassign issues and unassigned issues can be picked up:

Schermafbeelding 2025-07-30 112437.png

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management