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

Users of specific group unable to assign issues to users with proper permissions

Bhaskar_ppieq1

Suddenly users of specific user group not able to assign issues to different users of the project which they could able to do it previously. Other group users which has "assignable user" as well as "assign issues" still could able to assign.

I have checked the project permissions has both "assignable user" as well as "assign issues" permission for project. Users of this group are part of jira-software-users group which has browser user and group permission

Please advise on what would be my next steps to resolve this.

Accepted answers

All comments

Ravi Sagar _Sparxsys_

Hi @Bhaskar

Use the permission helpertool in Jira, it might give you some insights.

Ravi

Ilya Turov

you can go to that project's administration page -> Permissions -> Permission helper and try to find out "why a user does or does not have certain permissions"

Bhaskar_ppieq1

Thanks for your responses. I have checked the permissions(Assignable User and Assign Issues) for the user of that specific user group using the permission helper as suggested.

It says below

<<Specific User>> has the 'Assignable User' permission
<<Specific User>> has the 'Assign Issues' permission

It suggests that <<User>> is not in the jira-administrators group suggesting him to add to that group

My question is, this was working fine a week back and not sure why it is not allowing users to assign now

Appreciate more suggestions.

Thanks
Bhaskar

Ravi Sagar _Sparxsys_

In your Permission Schemes are permissions given to a user, role or a group?

Also check the Global Permissions and check who has "Browse Users".

Ravi

Ilya Turov

@Bhaskar

Judging by the fact that it was working fine last week and you didn't change anything in this project, the case might be that this permission scheme is shared between several projects and it was changed for another one without thinking that it might affect the one you are having issues with now.

e: in this case you can check audit logs for this scheme and see if anything was actually changed. Just go to System -> Audit Log and paste your scheme's name into a searchbar.