nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Removed version from project, now issues not visible on Kanban board - reset version for issue?

Zoltán Lehóczky

I had certain issues flagged with a version in JIRA. I removed the version (without removing it from the issues first) and now the affected issues aren't displaying on the Kanban board any more.

This is because the query of the board won't return those issues:

project = KEY and (fixVersion in unreleasedVersions() OR fixVersion is EMPTY)

This is because for the affected issues somehow the Version field is in limbo and is neither empty, nor containing a version... I tried to clear the value of the Version field through bulk edit, I also similarly tried to set a different version, then clear the field. However nothing will make the issues display, only adding another version to them. Re-indexing didn't help either.

How can I completely wipe out the Version field of these issues so they are matched by the query, or how can I otherwise solve the issue?

Thanks in advance!

Accepted answers

Mauro Badii

The problem is caused due to this bug: https://jira.atlassian.com/browse/JRA-22351

A database update is required to workaround the problem until the problem is fixed.

All comments

Nic Brough -Adaptavist-

If you delete a version, it should be stripped off the issues as well. How did you do the "remove" of the version?

Zoltán Lehóczky

Under Project admin/Versions. The version is not actually visible under the issues but still the above query indicates that the Version field is not empty.

Nic Brough -Adaptavist-

I apologise, I was not clear there. When you "removed" it, what do you mean? Merge? Release? Archive? Delete?

Zoltán Lehóczky

It was Delete.

Darren Pegg

The reindex should have fixed as Nic advised... maybe try renaming 3 folders within the caches/indexes folder found in JIRA install directory and then perform a locked re-index. Once completed remove these renamed folders which are (changes, issues, entities).

LakshmiS

change the query for the board to project = KEY

That should display the missing issues also. Check the version number for these.

Bulk update the version for the 'missing issues' to a consistent value other than empty, say 'LATER'

change the query for the board to project = KEY and version = LATER

Zoltán Lehóczky

I'm on Cloud so this is not an option unfortunately.

Zoltán Lehóczky

So if I understand correctly you advice adding a version to the affected issues. This is a workaround I though about (see the question) but I'd rather not have a version specified for the issues (this is why I removed the version in the first place) and would like to handle them as if their version would be empty, as it appears.

Darren Pegg3

Ahh so it is, putting a request into Atlassian support may help, though I doubt they will go into that level of support

Nic Brough -Adaptavist-

You're right, you really should not have to do this. It should be empty

Mauro Badii

The problem is caused due to this bug: https://jira.atlassian.com/browse/JRA-22351

A database update is required to workaround the problem until the problem is fixed.

Zoltán Lehóczky

Unfortunately this is the case.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

jira

cloud

jira-cloud