JQL Search returns two same custom field options whereas there is only one in the database and on custom fields page
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
問題
While performing a JQL search for a specific custom field, it returns more than one option whereas there is only one record in the database. There is no error in the logs.
診断
Run the query below and ensure that there is only one record for the custom field or for each context of the custom field:
select * from customfieldoption where customfield=(select id from customfield where cfname='YOUR CUSTOM FIELD NAME');We can accept the data in the database as consistent if the query above returns only a single option for each field/context.
原因
In a specific scenario, there is another record in the cache and the root cause of how this record stayed/appeared in the cache is still not known.
回避策
Update the related field option on UI and rename it twice (from original to another name and then from another name to its original name) to update the cached data.