User gets an empty dropdown for component field

[Jeffrey Hendrikse]

Hello,

In a company controlled Jira Cloud project multiple components have been defined. The field is visible on issues and has no restrictions on it. A user that is part of the project members role (which has the edit issues permission) gets a dropdown that says "no matches found" when clicked on.

This has been tested in Edge and Chrome browsers and I, as a site- and org-admin, tested it by logging in as the user and found the same issue.

Permission helper also says that the user should be able to edit the issue. Nothing has changed in permission schemes on our end.

When I click on the component field i do get the components that are available in the project.

I am quite lost, as this problem has only started recently and I am not sure why. Can anyone shed more light on this?

Thanks!

[Brad Flurer · Accepted solution]

I reported this bug to Atlassian customer support. They informed me this morning that the bug is fixed, and I confirmed on my end that the bug is fixed.

[Tomislav Tobijas _Koios_]

Hi @Jeffrey Hendrikse ,

Are you using Jira components or Compass components? I'm not familiar that there are any additional restrictions when it comes to components options. I've also tried to search for similar issues but couldn't find anything useful.

If you did try everything (such as logging in as user and such), I would suggest reaching out to Atlassian Support as they can do some background troubleshooting.
*if they do manage to find the root cause, I believe community members would appreciate if you could share that info here 

Cheers,
Tobi

[Jeffrey Hendrikse]

Hi @Tomislav Tobijas _Koios_

We use the standard Jira components, so no Compass.

I have reached out to support, if the problem can be resolved I will report back.

Thanks!

[Tomislav Tobijas _Koios_]

@Jeffrey Hendrikse great! As it seems others are also experiencing this, I would suspect there's an issue on Atlassian side. If the support team opens a Bug for tracking this issue, I think everyone would appreciate if you would share it here. 🙂

[Jeffrey Hendrikse]

Hi, it was indeed a bug, support stated the following:

We faced an internal issue due to which an unexpected behavior with Jira Components was seen.

Switching to Compass Components and then switching back was a workaround while our internal team addressed the issue at large. The issue is now completely resolved and the components are working as expected.

[Tomislav Tobijas _Koios_]

Glad to hear that. Thanks for sharing the info (and workaround) @Jeffrey Hendrikse !

[Anthony Kelly]

This issue is happening to one or more users within my organization as well.

[Brad Flurer]

I started experiencing a similar issue within the past few minutes, but I was not affected by this issue earlier this morning. I can only access "Recent components" in the "Components" ticket field. But if I try typing/searching any component name, I always get the "No matches found" search result.