Hide "Done" in Board and Backlog?

[Scott Beeson]

I'm using one of the recommended "next-gen" templates (KanBan) but after I mark a task as done it stays at the top of the backlog screen and in the "done" column on the board. Will these go away after some sort of time-out?  Is this configurable? I can understand them staying on the board in the done column, but they should immediately be gone from the backlog screen in my opinion.  I'm not using Sprints at all. I'm worried about what my backlog will look like in a couple weeks or months... 

[Scott Beeson · Accepted solution]

Just saw this today.  Hooray!

[Robert McFeely]

YAY

[Uma Sanjeevi]

if we do the clear x done issues - where are the cards move to ? 

i did move the done cards to backlog however i can't find them anymore .. it is only visible via the EPIC card. 

[Chris Hutchinson]

The option is greyed-out if you have grouping tickets on the board.

You need to GROUP BY None to be able to clear done issue.

[Uma Sanjeevi]

ok - but it actually works even by epic view.. 

i just have to clear by the column view. 

however to retrieve the cards - i have to view by search engine only.. 

[Eugene Pyvovarov]

@Petter Gonçalves for us it doesn't remove tasks from DONE status for months. When can it be fixed?

[Katrina Houghton]

@Petter Gonçalves @Jack Brickey We are seeing the same occur in the Next Gen Kanban board as well.  Done does not drop off the board for months.  Sprints are not enabled since for this project we don't have sprints.  Is there a setting that can resolve this?  Can We get an ETA on when this will be fixed?

[Jack Brickey]

@Katrina Houghton , i'm am but a user like yourself and in fact don't actively use NG projects so I can't speak to the current behavior definitively nor and planned changes.

[Petter Gonçalves]

Hello @Katrina Houghton and @Eugene Pyvovarov

Analyzing other similar requests, I found out some possible actions that could cause the issue to don't disappear after 14 days:

1 - The issue was already done before adding it to the board/before the board was created

2 - The 14 days rule will only work for the issues placed in the last column of the board. If the issue was transitioned to this column and at the time it was not the last column of the board, it the rule will not be applied if you move the column posteriorly

3 - The resolution of the issue is not being set (Check if the green flag is appearing in the issue card)

To fix any of the three possibilities above, I suggest you perform the following:

- Try to move the issue to the previous column and then move it back to the last column

- Try to create a new column to be the last one and move your issues to it

Let us know if any of the options above worked for you so we can properly inform it to our development team and check if it is expected or it's a bug.

[Lise Angell]

All 3 points above are checked, but our Done issues are still cluttering the rightmost column... 

[Dmitrii Eliseev]

Yep. Same for me. Doesn't work. Honestly, this is a really annoying and not-friendly feature...

[Ash Smith]

Can we change this 14 days limitation? It's really annoying for us to have a huge list of DONE tickets sitting in our backlog for 14 days,

[Jack Brickey]

I would definitely provide feedback to Atlassian via the feedback link.

[Petter Gonçalves]

Hello Ash,

unfortunately, it's not possible with JIRA next-gen at this moment.

Since next-gen is still a beta feature, our developers are focusing on improvements, like the one you mentioned:

- NEXT GEN - Enable/disable/config removal of issues in DONE column

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

[Lucy Walton]

Tasks in the "Done" column older than 14 days have been removed from the Kanban board but are still displayed on my Backlog list. Any idea why? From this thread it sounds as though the tasks should also be hidden from here.

[Petter Gonçalves]

Hello Lucy,

If you are using a Next-gen project, I believe that your done issues are not been considered as done and that's why it is being displayed in your backlog.

Next-gen projects understand that an issue is done when its status is mapped in the right-most column of the active board. Could you please check if that's the case in your kanban board?

If that's true, could please send us a screenshot your board columns and another screenshot displaying the details of one of the issues that keep appearing in your backlog?

P.S: Make sure you have hidden all the confidential information from the screenshots.

[Johan Lejdung]

Done issues are not considered done?

I've just dragged a ton of old issues into the board (which we had removed since they never disappeared). When can I expect them to go away? And can i adjust the number of days it says unarchived?

We currently have around 5x as many things in done as the rest of the board combined... 

[Eva Weiss]

Put the "DONE" ticket back in the backlog and refresh.

[Brendan Shaw]

This worked for us - we had some 200+ 'Done' that did not have the done tick.

This was due to how we setup the board and then later adjusted it.

This meant despite being done, they would not disappear from the board.

To force this, we used the Project Automation:

Trigger = Scheduled (that day using Cron 0 17 10 20 OCT ? 2020)

JQL = Status = Closed

 - Our 'done'

v

IF Status = Closed

 - Probably a redundant filter

v

Then Transition Issue to : Temp

 - A temp column created

v

Then Tansition Issue to : Complete

Once run, all 200+ picked up the done tick and we could clear with the new manual 'Clear Completed Items'

Downsides?

Spam mcspam spam emails

And 'age' of status change was reset to 0

 - Neither impacted us.

[Deleted user]

Hey guys please vote for this feature here - https://jira.atlassian.com/browse/JSWCLOUD-17582?_ga=2.265022735.1409859376.1559590104-21829331.1559590104

[Michele Dorigatti]

I added a quick filter "Status != Done". Handy,

[alain]

You should be able to remove Done issues by completing the sprint and creating a new one. The non-Done issues will be migrated to the new board.
It's not a bug, it's how SCRUM works. You need to see the Done issues in the active sprint to be able to do the sprint review and retrospective ceremonies.

[Johan Lejdung]

We don't use SCRUM though, we use KANBAN. 

[Robert McFeely]

Atlassian in my opinion have little continuity or ownership of issues.  They only care about acquiring new customers and hope the pissed off existing ones are too locked in to leave. Cynical

[Petter Gonçalves]

Hello @Robert McFeely

Sorry to see that you feel this way about the way Atlassian handle and prioritize feature requests. Please, allow me to provide you with a different perspective:

As you can see in our Implementation of New Features Policy, our product managers are reviewing the most requested features on a regular basis, considering not only the popularity but also other factors to make sure that feature will meet with the application goals, however, due to the high number of requests, sometimes it's may not possible to support all those requests in a short timeframe as 3 or 4 months.

Talking specifically about the request to remove done issues from Next-gen Scrum or Kanban boards, I can confirm to you that our Next-gen PMs are not ignoring the feedback provided by our customers and have clearly understood your goal here, that's why we are currently developing a way to customize Next-gen boards and properly remove done issues at any time you need, just like you can do in Classic projects.

As you can see in the public Next-gen Roadmap, it's our second most prioritized feature, so it will absolutely be implemented in the next few months:

Additionally to that information, I would like to point out that Next-gen projects were initially created to provide a simpler and straight forward solution with fewer customization options for the customers who felt overwhelmed by the complexity of Jira Classic projects.

However, based on all the feedback provided, we understand today that the best solution would be to provide a project template with the same functionality that Jira Classic does but with the option to turn-off undesired features and make it simpler. That's our goal today. :)

Please, let us know if you have any specific concerns or question which I can help with.

[Robert McFeely]

Hi Petter

I am glad that I got your attention and excellent transparency.  i am heartened with your response and take on board that Atlassian have quite the backlog.  I look forward to seeing this change

However please take on board that my frustration has come from a real place that in the in past I have read and commented on many cases and heard nothing from atlassian showing any such transparency that you have shown above.  

So in summary it seems your problem here is one of PR and transparency.  Give people an insight that the issue is real, understood, and cared for.  Even if it is amongst a very long list, users would still be happier because the tunnel, however long, has light.  

Thanks for listening

Rob

[alain]

@Robert McFeelyI'm sorry I have left you bewildered and exasperated but I would like you to notice 2 things"
- My comment is a possible solution, I use it all the time (On Kanban NextGen you can enable sprints. When you want to clear the board, you close the sprint and your Done issues are gone. Then you just open another one)
- I am in no way affiliated with Jira/Atlassian. I'm just a user that tried to support another user. I don't think your tone or criticism have helped much more than my attitude.

Thanks you @Petter Gonçalves for your detailed answer

[Robert McFeely]

Ah.  Sorry @alain .  I had thought you worked for Atlassian.  My bad.  I have edited my comment above to remove reference to your answer.  

In reference to my tone.  Unfortunately, from my experience, it is often only this tone of response, which I believe is constructive criticism, which has raised such a good a response from Atlassian.  Needs must.

[Petter Gonçalves]

Hey @Robert McFeely

Thank you one more time for all the reasonable and useful feedback provided.

I completely understand your frustration when you don't get a real transparent and vulnerable answer about am impactful issue in the application, and that's a problem that most IT companies are facing today: How to track this feedback and provide our customers with useful and transparent answer in an acceptable timeframe?

I just would like to assure you that we really care about your experience and feeling about our products and that we are currently working to get this communication lack properly addressed.

That being said, I will make sure your feedback also reaches our PMs, by adding it in an internal comment at the official feature request.

@alain thank you a lot for the instructions provided and for helping us to provide our customers with some different options. Although the initial question is about Kanban, the Scrum methodology is a good option for those users that need to get the issues off the final board column at any time by simply completing the Sprint. For that reason, your answer might be useful for other users in the Community.

Have a nice week ahead, folks!

[alain]

 Although the initial question is about Kanban, the Scrum methodology is a good option for those users that need to get the issues off the final board column at any time by simply completing the Sprint.

I would like to clarify that users don't need to switch to a Scrum methodology to use Sprint to clear the board. You can use a Kanban board and enable sprints just for the sake of cleaning up done tasks. Just remember to restart the Sprint after closing it and everything will be exactly the same as bare Kanban.

[Petter Gonçalves]

Hello Scott,

By default, if you don't have sprints enabled, the done issues will be automatically removed from your next-gen board after 14 days, including from the backlog view.

That's the current expected behavior for Next-Gen projects. Can you confirm if that's the case for you?

[Jack Brickey]

and if you do have sprints enabled then when you complete the sprint they disappear.

[Scott Beeson]

I will confirm in 14 days if these disappear...   One reason I picked this project type is because we don't do sprints.  Is there a way to change this "time-out"?

[Jack Brickey]

not in NG projects at least not currently. you may wish to provide feedback via the feedback link

[me]

Can these Done task be found another way after the 14 days or are they deleted?

[Jack Brickey]

sure...JQL search, e.g project = abc and status = done

[Kim Rojas Hernandez]

Hi @Jack Brickey is it still the case that we can't change the "time-out" of the disappearing issues after 14 days if sprints aren't enabled? Thank you

[Jack Brickey]

@Kim Rojas Hernandez , while I don’t use NG much here is what I found - Introducing-manual-board-clearing-for-your-next-gen-Kanban-board 

so its appears this issue has been resolved now.