I am using a kanban board and in the past have been able to successfully click on the "Release" button to clear out the done column on the board.
Since the UI update, I have not been able to clear the column. I checked to make sure there was a resolution. When I go to the release hub, there are no errors. After I click on release, it still shows the tickets.
By default Kanban boards have a sub-filter, and this has a default value of:
fixVersion in unreleasedVersions() OR fixVersion is EMPTY
If this is setup for your current board, then when the issues are released, they should then have a fixVersion value and no longer have null values for that field. The issues are still in the agile reports, but if your subfilter is set this way, you should no longer see these issues on the board itself.
I suspect that perhaps your subfilter for this board has been modified in some way. That is really the only way I can think as to why you could release issues and still see them on the board. It might help to take a look at our documentation on Adding a Sub-filter for Kanban boards for more info on this.
Thx for this. Related to this: is it possible to have a release JUST have 1 fixVersion (the tickets from this round of development)? Or is it expected that every release has every fixVersion that came before?
When you click the release button on the kanban board, it is expected to change any/all versions that exist in that done column from unreleased to released. You can see these in the Project administration settings under Project config -> Versions. This shows you all the releases/versions in this project. So in short, No, I don't know of a way to only make that release a single version, short of moving the other issues temporarily out of the done column before pressing release.
The idea here is that if you have released a version of your code/product, that these issues that belong to that version would then disappear here, because there is nothing more for you to do with those issues.
Thanks for the reply!
So to be clear it is expected or not expected that items created in 2013 continue to show up in every release? (I.e. with a long list of Fix Version/s attached to them.)
I have over a thousand issues in my latest version even though I only worked on a fraction of that number for this actual release. Just trying to figure out if I'm doing something wrong!
it is expected or not expected that items created in 2013 continue to show up in every release?
When the issue is created doesn't tell us anything about whether or not it should appear on the board. It's the subfilter that determines when issues disappear from a kanban board. If all these issues have a fixVersion set, but that specific version was never released until now, then I could understand why you might be confused by this.
Did you make any changes to your subfilter on this board recently? What value do you have for your subfilter on this board?
The board's sub-filter: fixVersion in unreleasedVersions() OR fixVersion is EMPTY
(To be clear, I probably shouldn't have hijacked this existing thread haha. My issue is not the same as the OP. We do not have any problem with "clearing" the done column. This just happened to come up in search first.)
My "issue" is that all tickets from all time are showing up in all versions/releases. And everytime I hit the release button, the current tickets are just getting added to an ever increasing list of old tickets.
This particular release may have only had 50 Issues worked on as an example but:
Any one ticket in all my releases seemingly gets a new Fix Version every time I hit the Release button.
I would expect any single ticket to only be part of 1 release.
Cool, we can delete this question here now if you like. I've noted the question and have the screenshots to post as a new question.
I have an upcoming Release in a couple days. If it happens again I'll post a new question.
In a way I guess it's good news that it sounds like what I'm seeing is actually unexpected.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
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