Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-17582

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

    • Icon: Suggestion Suggestion
    • Resolution: Done
    • None
    • None
    • 15
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      On next gen boards on Jira Software Cloud, issues which are moved to status 'DONE' are no longer visible on the kanban board after 14 days. I would like configure the time these issues remain visible (to be longer) or be able to disable the removal of removal of these issues. 

       

       

      Atlassian Status Update -  22nd June 2020

      Hi everyone!

      I'm pleased to announce that we have shipped to everyone the ability to manually clear your DONE issues at any timehttps://community.atlassian.com/t5/Next-gen-articles/Introducing-manual-board-clearing-for-your-next-gen-Kanban-board/ba-p/1411958#M1379

      Regards,

      Ivan Teong

      Product Manager, Jira Software

       

      Atlassian Status Update -  21st May 2020

      Hi everyone!

       

      You'd be pleased to know that we have the feature ready for rollout to some customers for early access!

      If you want to be the first cohort of customers to get this feature, please register here: https://forms.gle/bv9HCdLbARfoXrLo6 

       

      Let me know if you got any further questions.

      Regards,

      Ivan Teong

      Product Manager, Jira Software

       

       

      Atlassian Status Update -  6th April 2020

      Hi everyone!

      I'm Ivan, a Product Manager in Jira Software, and I wanted to update everyone that my team is currently working on the ability to manually clear issues in the DONE column on an ad-hoc basis. Please be patient as we just wrapped up our discovery research and design spike, and will be undergoing development work in the next few sprints.

      With regards to finding issues that have been cleared from your DONE column, you will be able to do that through the new ISSUE NAVIGATOR in next-gen as stated here https://community.atlassian.com/t5/Next-gen-articles/Introducing-issue-navigator-in-next-gen-projects/ba-p/1339049, which will ship before manual board clearing.

      Regarding bringing already-cleared issues back to the board (which we don't encourage as it might be better to create a new issue instead reflecting the latest thinking about that work), you can simply change the status of the issue.

      Let me know if you got any further questions.

      Regards,

      Ivan Teong

      Product Manager, Jira Software

       

            [JSWCLOUD-17582] NEXT GEN - Enable/disable/config removal of issues in DONE column

            Hello Mr. Ivan Teong, (Product Manager, Jira Software),

            In your Atlassian Status Update -  6th April 2020, you have mentioned the below.

            ------------------------------------------------------------------------------------------------------------

            Regarding bringing already-cleared issues back to the board (which we don't encourage as it might be better to create a new issue instead reflecting the latest thinking about that work), you can simply change the status of the issue.

            ------------------------------------------------------------------------------------------------------------

            We would like to have all items with DONE status to remain on the board. Also we are not doing any manual clear, still the Done items are getting cleared after some time automatically from the board.

            Based on your suggestion above, just to get back all the Items with Done status back onto the board, we manually changed the status of all the issues with Status Done to something else to bring it back to the board & then again put them back in the Done Status, but they still disappear automatically after some days.

            Pls help us with this. It is very important for us to retain all the DONE items on the board.

            Thanks,

            Adil

            Givaudan.com 

            Adil Bulsara (ADIL) added a comment - Hello Mr. Ivan Teong, (Product Manager, Jira Software), In your Atlassian Status Update -  6th April 2020 , you have mentioned the below. ------------------------------------------------------------------------------------------------------------ Regarding  bringing already-cleared issues back to the board  (which we don't encourage as it might be better to create a new issue instead reflecting the latest thinking about that work), you can simply change the status of the issue. ------------------------------------------------------------------------------------------------------------ We would like to have all items with DONE status to remain on the board. Also we are not doing any manual clear, still the Done items are getting cleared after some time automatically from the board. Based on your suggestion above, just to get back all the Items with Done status back onto the board, we manually changed the status of all the issues with Status Done to something else to bring it back to the board & then again put them back in the Done Status, but they still disappear automatically after some days. Pls help us with this. It is very important for us to retain all the DONE items on the board. Thanks, Adil Givaudan.com 

            Hi Ivan, I do not see the three dots when I hover over the Done column so that I can clear those issues from the column.  Is there another way to perform this action?

            thy.guintivano1 added a comment - Hi Ivan, I do not see the three dots when I hover over the Done column so that I can clear those issues from the column.  Is there another way to perform this action?

            Hello Ivan,

             

            Is there a way that I can increase this limit of 14 days for the Done issues to disappear from the Board?

             

            Regards,

            Abdullah

            Abdullah Masood added a comment - Hello Ivan,   Is there a way that I can increase this limit of 14 days for the Done issues to disappear from the Board?   Regards, Abdullah

            fabian added a comment -

            Hi everyone,

            is there any update on the default 14 day removal timer? I would like to configure the time for this automation myself or even better, disable this automation entirely.

            Cheers,

            Fabian

            fabian added a comment - Hi everyone, is there any update on the default 14 day removal timer? I would like to configure the time for this automation myself or even better, disable this automation entirely. Cheers, Fabian

            Hello, Ivan,

            Based on the description, it doesn't seem like this is Done. Part of the request was to allow configuration to not hide issues after 14 days (or change the timeframe):

            I would like configure the time these issues remain visible (to be longer) or be able to disable the removal of removal of these issues

            You can still not disable the removal of issues or extend/reduce timeframe for removal. Am I missing something?

             

            Cheers,

            Tyler

            Tyler Brown added a comment - Hello, Ivan, Based on the description, it doesn't seem like this is Done . Part of the request was to allow configuration to not  hide issues after 14 days (or change the timeframe): I would like configure the time these issues remain visible (to be longer) or be able to disable the removal of removal of these issues You can still not disable the removal of issues or extend/reduce timeframe for removal. Am I missing something?   Cheers, Tyler

            67ff05bb51a9 You mentioned "The length of the sprint is tied to the expected frequency of delivering value (not releases, but valuable increments) to our shareholders." and "Inter-departmental iterations happen often." Does that mean that your sprint length varies quite often and is not really kept to 2 weeks (recommended by Scrum.org) and that you have a lot of new issues added to the sprint after the sprint has started?

            Ivan Teong (Inactive) added a comment - 67ff05bb51a9 You mentioned "The length of the sprint is tied to the expected frequency of delivering value (not releases, but valuable increments) to our shareholders." and "Inter-departmental iterations happen often." Does that mean that your sprint length varies quite often and is not really kept to 2 weeks (recommended by Scrum.org) and that you have a lot of new issues added to the sprint after the sprint has started?

            Thank you for your response, Ivan. We are not looking to remove the issues, but just to hide most of them from immediate view. We are a rather large team that needs to have a common board because the project is very interdisciplinary and the bigger picture is crucial to how each task is resolved. Inter-departmental iterations happen often. The length of the sprint is tied to the expected frequency of delivering value (not releases, but valuable increments) to our shareholders. Finally, in next-gen there is only one board per project and no cross-project boards, so our hands are tied there. People get overwhelmed when they open the board and see more than 6 items per column, which makes them less productive. Something like "click to view more" would be highly appreciated.

            Crina-Maria Ionescu added a comment - Thank you for your response, Ivan. We are not looking to remove the issues, but just to hide most of them from immediate view. We are a rather large team that needs to have a common board because the project is very interdisciplinary and the bigger picture is crucial to how each task is resolved. Inter-departmental iterations happen often. The length of the sprint is tied to the expected frequency of delivering value (not releases, but valuable increments) to our shareholders. Finally, in next-gen there is only one board per project and no cross-project boards, so our hands are tied there. People get overwhelmed when they open the board and see more than 6 items per column, which makes them less productive. Something like "click to view more" would be highly appreciated.

            67ff05bb51a9 This only works for Kanban, because Scrum (sprints-enabled) projects will clear DONE (resolved) issues when the sprint is closed. Also make sure that all your subtasks for your parent issues are completed, otherwise the parent issues won't clear.

            I don't recommend trying to clear the issues before the sprint ends, as that is part of the sprint scope and provides visibility to what was in the sprint. If there is excessive work in the sprint, it might be worth thinking about shortening the sprint time period.

            If this is still a problem for you based on your team's use-case, feel free to elaborate further and we can advice.

            Ivan Teong (Inactive) added a comment - 67ff05bb51a9 This only works for Kanban, because Scrum (sprints-enabled) projects will clear DONE (resolved) issues when the sprint is closed. Also make sure that all your subtasks for your parent issues are completed, otherwise the parent issues won't clear. I don't recommend trying to clear the issues before the sprint ends, as that is part of the sprint scope and provides visibility to what was in the sprint. If there is excessive work in the sprint, it might be worth thinking about shortening the sprint time period. If this is still a problem for you based on your team's use-case, feel free to elaborate further and we can advice.

            This is a great feature, but only works for Kanban, which is not explicitly mentioned in the definition of done for this ticket. the relationship with Kanban is mentioned in the description just as an example. Is there another ticket where this functionality is covered for SCRUM? 

            Crina-Maria Ionescu added a comment - This is a great feature, but only works for Kanban, which is not explicitly mentioned in the definition of done for this ticket. the relationship with Kanban is mentioned in the description just as an example. Is there another ticket where this functionality is covered for SCRUM? 

            e4e3e5c90227 It should work. It's been rolled out and only exist for next-gen boards without sprints enabled. See the blog post's comments to see if there is something related to the column configuration: https://community.atlassian.com/t5/Next-gen-articles/Introducing-manual-board-clearing-for-your-next-gen-Kanban-board/ba-p/1411958#M1379

            Ivan Teong (Inactive) added a comment - e4e3e5c90227  It should work. It's been rolled out and only exist for next-gen boards without sprints enabled. See the blog post's comments to see if there is something related to the column configuration:  https://community.atlassian.com/t5/Next-gen-articles/Introducing-manual-board-clearing-for-your-next-gen-Kanban-board/ba-p/1411958#M1379

              iteong Ivan Teong (Inactive)
              ecd05919680b Casper Stevenaar
              Votes:
              446 Vote for this issue
              Watchers:
              171 Start watching this issue

                Created:
                Updated:
                Resolved: