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

Unable to assign issues to users even with proper permissions

Tarkan Serim

None of our users (including admins) are able to assign issues to users. When we click the assignee field and type in any name, nothing is returned. The project has "any logged in user" permission for "assignable user" as well as "assign issues". When I check the users names from the permission helper, Jira tells me that the users do have permissions (both for assigning and being assigned).

We do have Post-Functions to assign issues automatically to different users for different steps in the workflow. I am wondering if this makes a difference. Although the issues were still assignable to anyone for a few days before this behavior started happening.

(using Jira cloud)

Accepted answers

Tarkan Serim

After working with the support team, turns out the issue was the fact that the "Assignee" field was not in the "View/Edit Issue Screen" for this particular project. Although the filed was still showing on the actual issue details, and was also present in the "Issue Layout" menu (for the new issue layout), since it wasn't on the View/Edit Issue Screen, users were not able to update it.

Once the Assignee field was added to this screen issue was resolved.

All comments

Ignacio Pulgar

There have been some changes in order to improve privacy and to better algn with GDPR.

"As part of an effort to consolidate user profiles, we're phasing out usernames in favor of using full names and public names when users are searched for and referenced in Jira Cloud and Bitbucket Cloud."

Apps that you or your users may have installed in Atlassian cloud products are being updated to protect your users' privacy.
What this means for your users:
• They'll be able to control who can see the information on their profile.

• Their profile information may look different depending on who's viewing it.

• They aren't able to do things like search for users by their usernames anymore.

• Their public names, instead of their full names, will display on community-oriented Atlassian sites, such as Atlassian Community and jira.atlassian.com."

Tarkan Serim

@Ignacio PulgarI appreciate the information, but I might be missing the connection between your answer and my question. Could you please clarify if there is any link between the two?

Ignacio Pulgar

After reading your question a second time and having tested a bit, my initial answer has no relationship with it. Sorry for that.

Please, double check with the Permission Helper that people count with the permissions you mentiomed and Browse Projects.

If they have all permissions, open a ticket to Atlassian Support.

Ignacio Pulgar

Hi Tarkan,
Did you finally raise a ticket with Atlassian Support?
https://support.atlassian.com/contact
Regards.

Tarkan Serim

Yes, I was able to reach out and resolve the issue. I will write out the resolution here so others can reference in the future if they run into the same situation.

Tarkan Serim

Once the Assignee field was added to this screen issue was resolved.

Ignacio Pulgar

Oh, I see! Thanks for the update!

Chesco Igual

Solved for us, thanks! Super straighforward as usual

Welcome!

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

Quick Links

Find more posts tagged with

jira