Custom field select list options not available in screens

[Jennifer Haag]

When editing an issue (new or old), the stored options of the select lists are not displayed. Instead it says "no matches found".

This happens with all custom select lists in all our projects.

When checking the configuration of the custom fields and the screens, everything seems fine, but it is not working in the live issues.

Custom field options or any related settings have not been modified recently.

[Rilwan Ahmed · Accepted solution]

Hi @Jennifer Haag  / @Maciej Walczak  @phwalker 

There is an active incident reported related to single select custom fields and you can find the status in https://status.atlassian.com/ and https://jira-software.status.atlassian.com/

[Rilwan Ahmed · Accepted solution]

Hi @Jennifer Haag ,

Welcome to the community !!

Please check below items:

1. Go to Admin settings --> Issues --> Custom field. Check if the field has any values added to it.
2. Go to Admin settings --> Issues --> Custom field. Search for the custom field and check if there are any contexts added to the field and it is not mapped to the required projects/issue types.

[Jennifer Haag]

Hi @Rilwan Ahmed

thanks for your reply.

1. Yes, there are values available to the fields.

2. Yes, the required context is added and required projects are mapped.

[Peter Bruning]

I found that making any change to the associated screen seems to resolve the issue (i.e. remove and add a field back in)

[Jennifer Haag]

This solved it for me, thank you!

[Peter Bruning]

This is also causing problems when the affected Custom fields are used in JQL based filters. Renaming them (if possible) seems to resolve it

[Maciej Walczak]

Hello, I have a similar problem.

I can select options from the list to set them as custom field values when I create a task, but I don't see anything in the list when I try to edit the task. All I see is "No matches found".

[phwalker]

I have also had this as of this morning in our projects - all working fine until today

[phwalker]

@Rilwan Ahmed seems like a wider problem than one instance?