Upgrading JIRA from 6.0.4 to 6.1.2 broke Custom Issue Type filter?

I upgraded our test JIRA instance from 6.0.4 to 6.1.2. Previously we had a simple filter, literally:

issuetype = Admin

where Admin is a custom issue type, that showed two results, the single Admin issue in two different projects. In 6.1.2, the same filter shows only one of the two Admin issues, but not the other. What would cause this?

1 answer

It looks like a case of broken index, can u reindex and test again?

That seems to have done the trick. I've upgraded JIRA several times across multiple major versions and have never seen this problem - what was the likely cause of the busted index?

During an upgrade the database often goes through changes, and it is always recommended that a reindex is performed.

I would n't say it was a busted index but just that a reindex was required which you missed.

Rahul

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 ...

3,316 views 14 20
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