Problem:
When searching under the filters tab in Jira using JQL the fields appear twice.
This does not happen when using the Basic search or when searching within any Jira Service Management or Work Management project.
When you attempt to select one of the field options it may or may not select the field. Ex. If you select the first "Customer ID" field it will select it. However, if you select the second "Customer ID" listed it will instead show "Customer Name [Dropdown]" ensuring the second option can not be selected.
Troubleshooting so far:
I have looked under admin > Custom Fields and have not found any double fields.
Looking at all other search options besides filters(searching within a project, creating a queue in a project, etc.), I notice that this does not appear to be a problem
It could be that this is related to Team managed projects where each project and associated custom fields are unique. So, while they are the same name there are actually different fields. Based upon your image I think that is what you are experiencing. If you are interested in a specific TMP project I suggest going to that project page and select the Issues page. From there construct your search by adding the desired qualifying JQL components.
I was thinking this may be the case because we have team and company managed projects.
However, the user who originally flagged this problem told me they had not seen it before today but no new projects have been created lately or had permission updates and I was able to replicate the problem.
The other concerning problem is not being able to select the second instance of the field to figure out which projects that this might be associated with.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Amelia Giuliani ,
Issue is reproduced for me too.
There is an active incident. This could be impacting it. You can subscribe to the incident to get the alerts
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't believe the active incident is the cause here but certainly could be wrong.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you so much for the information! I was feeling crazy - glad it's not just me. I'll keep an eye on the status updates.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.