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

Assignable Users permission keeps reverting after I make changes

Allison Stewart_nejvgh

Hi,

I have a service project (cloud) where different support groups can work on issues based on the type of issue. For instance, Business Applications issues are worked by support team "AppSupport". IT technical issues are worked by support team "HelpDesk".

I have groups for these agents and have assigned users to their group. I have a custom field called Support Team that is shown on my issues to denote who owns the ticket and what agents can be assigned to it.

I have set the Assignable Users permission on my project to Admin and "Group custom field value" = Support Team.

I ONLY want the people in the group associated with the Support Team to be able to be assigned this issue. I do not want all Service Desk Team members to be in that list of possible assignees.

assignable user permission bug.jpg

This works when I update it. It works great! For awhile and then randomly, the system will revert and put Service Desk Team members and "add-on access" back in that permission. And I can "ignore errors" but then they come back.

What is going on? Do I need to update this somewhere else too? Do I need to do something different? How do I get this to stick?

Any help would be greatly appreciated as this is a critical issue for us. I can't go live without this working.

Thanks!!

Accepted answers

Nic Brough -Adaptavist-

The permissions that are being added back in are required for automation and other apps to do their jobs.

The warning about the service desk team role is there to tell you that you've mis-configured the project and you need to add the permission back.

This happens because JSM is a layer over a core Jira, and the core Jira allows more flexibility in the permissions. JSM has some requirements for permissions to be shaped in a certain way, but it can't stop core Jira allowing those changes, it can only warn about and fix the problems after someone mis-configures the permissions.

So, the "fix" for this is actually for you to stop trying to break the permissions.

All comments

Nic Brough -Adaptavist-

The permissions that are being added back in are required for automation and other apps to do their jobs.

The warning about the service desk team role is there to tell you that you've mis-configured the project and you need to add the permission back.

So, the "fix" for this is actually for you to stop trying to break the permissions.

Allison Stewart_nejvgh

Thank you for the response. But that "fix" won't work for us. We must be able to restrict the assignable users on the tickets based on a user group assigned to that ticket. We cannot have all of our service desk team members in one list, it'll be too hard to manage.

I'll ask around for other solutions to this problem and see if any one has a good "fix".

Cheers.

Nic Brough -Adaptavist-

There is no other way to "fix" it.

1) You need permissions that work

2) The role being added back in is for automations. This only goes wrong if you manually add humans into that role which is something you should not do.

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