Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Product Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

One Agent does not have access to the component list

Jonathan Caillouey
Jonathan Caillouey January 9, 2025

Hello everyone,
I’m facing a rather strange issue. Since this morning, one of the ServiceDesk agents can no longer select the component for an incident.

When they click on the field, it says "no matches" even though the field is empty.

The other agents are not experiencing any issues.

The component list has been in place for many years and hasn’t had any recent updates.

Any ideas?
Thanks in advance for your help.

Answer
Watch
Like # people like this
78 views

1 answer

0 votes
Alexander Pozdnyakov
Alexander Pozdnyakov
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
January 9, 2025

Same issue. [Jira]

View More Comments
Mikael Eriksson
Mikael Eriksson
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
January 9, 2025

Same here. I am that user in our organization :(

This is how it looks in an issue.
jira_issue.png

But if I go to the escalation menu all components are still there
jira_issue1.png

Like
Jonathan Caillouey
Jonathan Caillouey January 9, 2025

Thanks for the workaround.
It's OK from a workflow page.

The problem remains on the main incident page.

Like
Reply

Suggest an answer

Log in or Sign up to answer
Jira Service Desk
Jira Service Management
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events

    See all events