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

A single user can´t search issues

Hi all!

I have a really strange problem with one single user.

I import users (~500) from different active directories into my jira, everything works fine except one user. That user has (really) the same groups and projectroles as others, but when he searches for issues not a single issue can be found (so the dashboard is empty, too) (tested on different systems).

Despite that he can acces his issues by the quick search or by url...

The projectroles this user (and most others) is in can only see their own reported issues.

When I give him a projectrole able to see everything, he sees everything ...

I really don t know what to do with that... Your help is really appreciated.

Accepted answers

Thanks to all of you for your help. Problem was caused by different cases of users accountnames in the synchronized Active Directory and Jira. In detail, cwd_user and external_entities tables in database, for example j.kypke vs. J.Kypke.

All comments

Nic Brough -Adaptavist-

Searching respects permissions - if he can't see a project or issue, it won't come up in the search results.

You say he can only see his own reported issues - has he actually reported any?

This user has reported 18 issues and can access that issues (by quick search and url) but not by filters.

Nic Brough -Adaptavist-

When you say "access by quick search", do you mean just typing the issue key in? Or by putting a proper search in (project key, then words from the summary)?

By filters, I assume you mean you're putting in something like "reported by myself" and seeing the issue navigator return nothing?

I ask because there's an important question about indexing here and those questions will clarify it a bit.

Oh, and also, check that the user is not duplicated? If they're logging stuff as one ID and searching as another. (Doesn't sound like it, but needs explicitly ruling out)

Hi Nic,

thanks for Your efforts! With "access by quick search" I mean typing the issue key in the searchfield within the menu bar in the upper right corner of the screen.

"By filters" means searching for issues with the issue navigator (simple search or advanced with JQL).

I checked the user in the database before: there is only one user with that username in table cwd_user and only one corresponding entry in external_entities.

Radu Dumitriu

Can you install this: https://marketplace.atlassian.com/plugins/com.keplerrominfo.jira.plugins.rightsdna

and make sure that there's no problem with the permissions ?

Go to plugins->Rights DNA->Issue Security -> enter issue number and check the sources.

Alternatively, go to "By user", type in the user and see what perms s/he has. You may have enough info to decide if there's a perm problem.

Nic Brough -Adaptavist-

I'm not sure you need to bother.

User can see the issue when using the direct url. User can't get it in searches. Other users can.

There's no permission that separates that - if a user can see an issue, it should come out in the search, assuming it matches the search criteria.

(In most other "user can/can't", this advice is good, but I think Jochen has already covered it in his investigations)

Jobin Kuruvilla [Adaptavist]

Maybe look for errors in the logs when that user executes the JQLs?

Radu Dumitriu

@Nic You're right, if there's no bug. Assuming there's no error what he describes seems to be a bug in the perms IMHO. Or, the JQL is too simple and it is a problem in the search which I find it hard to believe.

Alternative scenario: There are 2 users with the same name (defined in 2 different directories, one local, one in AD, for instance) Older JIRA versions had problems with that, etc etc

Edit:

@Jochen L

I'm not saying you must buy this plugin. Just install it, check if the permissions are ok or not, then you can uninstall it.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jql

permission