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!
Ok, that sounds like a bug - when I delete a version on the demo system I have here, it is removed from all the affects/fix version fields in my project Could you try re-indexing the project (in the project admin screen) and check the Kanban board again?
Ok, this definitely needs to go to Atlassian support. The query "project = Key and fixVersion is empty" should be returning these issues (assuming there was only one fixVersion, and that's the one you deleted). The next step would be to read the logs, but you can't on Cloud. It's definitely broken, and they need to take a look for us.
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).
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
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.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG