It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Kanban board showing released issues

I am trying to migrate an existing project to Kanban. I create a new Kanban board from the existing project and when I go to the work board, all the issues are displayed. I tried to do a 'release' to clean things up but it runs forever (8+ hrs for 2200 issues) and doesn't stop. The activity log shows it is adding a fix version to the issues but they still show up. I have tried various filter settings but haven't been able to make them go away.

How can I make old issues not appear?

UPDATE: In trying to clean up this, I was removing the releases and noticed that even in removing the release tags, JIRA can't seem to handle the volume of changes? Sometimes it will remove a couple hundred tags and sometimes over a thousand but never any indication that something failed. In the case of making a release, it never makes any of them appear to be released even though they have release labels on the issues? What else needs to be changed to make them be 'released'?

UPDATE 2: So I got rid of all my old issues by unarchiving those releases and marking them as releases but that still didn't solve the problem. When I have issues in the tested/done column it says it will 'release' them and it appears to but they just don't go away. Even after cleaning up everything and essentially starting new, they sit there. The releases are 'released', the filters is unchanged and as near as I can tell, it should be working but it doesn't. The only thing that is possibly causing it - the QA tester marking them as "resolved" doesn't get the dialog that allows him to choose a resolution like "fixed" but I can't figure out why that would make any difference.

1 answer

1 accepted

Hi kevin,

One common situation the issue won't be released is when the "Fix Version" field has a version that is either "Unreleased" or "Archived" in the project.

If that is your case, I would recommend that you verify the version of your issues and verify if the version from the "Fix Version" field, is set to "Released" in the project. You can do this by clicking on the right icon of the version affect by your issue. Like in this image below:

Please let me know if you have any doubts!


Henrique Lechner

Henrique, Thanks for the pointer. They were all "Released".

Finally, after stopping to think about this, I realized that our previous way of doing things with using versions as iterations was breaking the filter. There was always one 'unreleased' version holding the current issues being worked on.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Software

[New] Jenkins for Jira Software Cloud and a way to connect your hosted apps

Jenkins is the leading open-source automation server used by startups and enterprise teams to build, test and deploy code to production.   We are excited to announce an official integration betw...

2,095 views 1 19
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you