How can a query/filter give different results after renaming one field value?

Hi,

This sounds like a bug; if so I'll file it anyway, but perhaps this sounds familiar to some.

I have a saved filter. One criterium is the selection of a certain value (custom field, multiple values possible to be selected simultaneously). Now I added some more possible values and slightly renamed the to-be selected value.

The search results yielded about 60 issues first, now only about 30. When looking at the missing ones, nothing seems to be wrong, they do match the search criteria including the custom field value.

After a warning in the Issue Navigator (in advanced searching) that the value could not be found anymore, I changed it in the filter to the new value and saved. Strangely, in Simple Searching or using the filter shortcut itself, no warnings are seen. A similar filter that I have is still unchanged, also delivers about 50% of the expected results and states the 'old' value in the summary of the filter, still yielding the (about 50%) of issues with the renamed value...

When I manually edit a missing issue and simply re-enter the to-be selected value of the custom field, the issue reappears in the search results after refreshing in the Issue Navigator. However, this means that any other values that were selected need to be deleted first and added back later (or any other should be added first and deleted later; i.e. 'something' needs to be changed in the selected values).

Also completely new searches reveal the problem, even when only selecting the Project and that one to-be selected value.

Any idea?

1 answer

1 accepted

1 votes

Hello,

It sound as the JIRA indexes got messed up after you renamed the fields, and it appears you've not re-index after doing so. If making any changes in any of the following areas, it is advised to re-index JIRA to avoid these kind of problems:

See: Re-Indexing after Major Configuration Changes. To try fix this issue, could you re-index JIRA?

I hope this helps!

Cheers,
Matheus Fernandes

Also, when editing an issue in JIRA, the issue is automatically indexed, hence it would then appear in the issue navigator. ;)

Indeed, I found this out yesterday, never realised re-indexing can be so important. After having performed one, everything was fine again. Thanks!

Yeah, JIRA uses indexes so it will provide faster searches with a minor performance impact. But if the indexes are out of date.... :P

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,760 views 11 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot