After editing custom field, JQL on kanban board swimlanes is outdated

[Yuri Suppa]

Hello,

I`ve updated a custom field options (dropdown choice type) and I am able to find the correct options if I run a JQL query from the filter search, even tho also the previous values are present.

I selected the search template in the Custom field settings already.

However if I try to create swimlanes on the project`s kanban board and want to use the a jql filter with this custom field, I only get the previous values and get an error if I manually enter the new ones. The error says: The option "x" for field "y" does not exist.

Since it is jira cloud there is no re-index options afaik so I don`t know how to fix this.

Thanks in advance

[Marta Woźniak-Semeniuk]

Hey @Yuri Suppa How long ago did you make the changes? I would give it 24h - JIRA should reindex in the background after such change but it's only software, it can have its "humors" 

[Yuri Suppa]

Hello @Marta Woźniak-Semeniuk  yes in fact I did the change yesterday, will check again tomorrow since as of now there are no updates

[Yuri Suppa]

nope! checked after a couple of days and still not updated

[Alexander Schäfer]

I am having exactly the same issue at the moment. And I also waited more than 24h (several days in fact) but I get the same error message.  @Yuri Suppa could you resolve your problem?

[Yuri Suppa]

nope. after all these days I still have only the original values for the custom field. None of the edited ones are visible. I had to use other fields to build my swimlanes.

[Alexander Schäfer]

@Yuri Suppa  In the meantime I could resolve my problem. The issue was a special character in the option of my dropdown field. I had the german character "ß". After I removed it from the string, the option could be selected in the JQL swimlane filter. Maybe removing non english "special" characters can also resolve your problem.

[Yuri Suppa]

hello @Alexander Schäfer thanks for your suggestions. I went to check and there was no special character however now I find all my correct updated options. Since nothing was changed in the custom field I think this was due to "late" indexing.