Hi there, I'm an administrator of a project within a Service Management Group.
Despite belonging to the same Administrators permission group as the Project owner, I am unable to filter by creators or assignee's. When anything is entered in these filters fields, I'm presented with this error
"The jira server was contacted but has returned an error response. We are unsure of the result of this operation"
The project owner is able to filter by assignee's/creators. I'm tech-literate, and have attempted to troubleshoot the issue with the owner (also tech literate).
We've checked user and project permissions as suggested here: https://community.atlassian.com/t5/Jira-questions/Cannot-filter-issues-using-assignee/qaq-p/1511628
Everything is setup correctly. There is no discernible permission difference between myself and the project owner. our Administrators role has access permissions for every part of the project. I've tested other browsers, checked with one other Administrator in the project group (they also return the same error).
I understand that I clearly don't have access to the people list filter in searches for the project (despite being able to browse all of the people within the project and see their permissions/details).
What's going on here? This is a wildly unintuitive and frustrating problem to try and troubleshoot. Any help is appreciated, thanks.
EDIT: The owner can send me a copy/pasted link with the relevant assignee/creator filter that he's already applied which allows me to see the filtered results, I just can't do it myself. Ridiculous.
Welcome to the community. Can you advise where are you encountered the issues (i.e. while trying to create a new JQL search referring to reporter/assignee)? It is strange that project owner is not having the same issue.
Once we obtained your update, we will be able to advise further actions/suggestions.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
Viasat Inc.
Hi Joseph, this issue is encountered under Search > Advanced Issue Search (basic search, not JQL) for all projects. no other filters applied.
I'm attempting to review reports generated by other project members, so initially encountered the error when clicking +More > Creator > then trying to put a project members name in the Creator filtering field (Enter username or Group). Doesn't matter what's typed in this field, the first character generates the error.
Decided to also test with the assignee field which generates the same error leading me to believe it's an issue with ability to access a list of the other project members.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Reuben:
Thanks for your update. What is your access role setup against your JSM project(s)? As you are having the issue with the following UI example -
Have you tried to use the above "Basic search" UI just against a project that you have access against to? For the project that you are having the error, can you see if you have the minimum role assignment of the "ServiceDesk Team" for that project?
Let me know of your findings.
Best, Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Joseph, my permissions level for this project is "Administrators".
Both "ServiceDesk Team" and "ServiceDesk Customer" are disabled.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you try to switch the UI to "Switch to JQL" and just enter "project = <the specific project name or project key>" and execute the search? Let me know if you get any error and obtain result?
If the execution of the query works, then retry the the search again using the "Basic" mode.
Best, Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Joseph, JQL searches work fine (and I'm able to include assignee/creator query strings without issue). It just seems to be a problem with the basic search GUI.
I'm just gonna use JQL strings going forwards, but there's definitely something wrong with the basic search application of filters in this case.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your update. In this case, I would recommend that you contact Atlassian Support (https://support.atlassian.com) for direct assistance on the oddity that you have encountered using the basic search functionality.
If my assistance helped you, please click on "Accept answer" when you have a chance.
Best, Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.