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; } } }

One of my Jira projects keep all issues in the closed column even after being released

Jimi Wikman_ex43zi

One of my Jira projects, which is a Kanban board, keep all issues in the closed column even after being released.

This is very odd since all issues should be removed from the closed column when the kanban board is released?

Has anyone seen this before or have a guess as to why this would happen?

Accepted answers

Tansu Akdeniz

Hi @Jimi Wikman

Kanban board uses the "Sub-Filter" to remove issues from the board. Default filter is "fixVersion in unreleasedVersions() OR fixVersion is EMPTY". Could you check your filter in case there is a difference?

All comments

Tansu Akdeniz

Hi @Jimi Wikman

Jimi Wikman_ex43zi

So it does not remove based on release at all, it just checks to see if the fixversion is set? That is interesting...Is this the same on DC, or is it just for cloud?

Tansu Akdeniz

This is same for all Jira's. If you click "Release" button in Kanban board, it assigns fix version to the issues in done column and issues are disappeared from the board.

Jimi Wikman_ex43zi

Thank you @Tansu Akdeniz

I must be getting old because I don't remember ever doing this back in Jira 6 and 7 and I find it a bit weird since that is not how the Scrum board works and I would assume they used the same functionality.

Anyway, I appreciate the quick reply.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud