• Icon: Sub-task Sub-task
    • Resolution: Fixed
    • None
    • None
    • None
    • None

      Right now, the only way to "hide" issues from next-gen boards is by deleting the issue or archiving the issue.

      The issue will be archived 14 days after you move it to the last column of your board.

      Please create the option to Hide issues or create the column mapping as the classic board so users can leave issues under a column that is not mapped.

       

            [JSWCLOUD-17295] Ability to hide issues from next-gen boards.

            Eoin added a comment - https://community.atlassian.com/t5/Next-gen-articles/Introducing-manual-board-clearing-for-your-next-gen-Kanban-board/ba-p/1411958

            Josh Evans added a comment -

            I'm here to watch, vote and add another voice to the comments above. By definition, "Done" work is not part of a board; "Done" is shipped work.

            Above commenters are correct to point out the troubling semantic problem with treating this ticket as the ability to "hide" tickets. That is not the ask!! We are asking that the board view (within backlog) respect the "Done" status.

            Josh Evans added a comment - I'm here to watch, vote and add another voice to the comments above. By definition, "Done" work is not part of a board; "Done" is shipped work. Above commenters are correct to point out the troubling semantic problem with treating this ticket as the ability to "hide" tickets. That is not the ask!! We are asking that the board view (within backlog) respect the "Done" status.

            An update on this problem is appreciated! I have the same problem, a backlog of done tickets that creates a lot of visual noise on the screen.

            Norm Malloch added a comment - An update on this problem is appreciated! I have the same problem, a backlog of done tickets that creates a lot of visual noise on the screen.

            celeste added a comment -

            Our 14 day archiving not working either, they stays in the done column and has no where to go 😞

            celeste added a comment - Our 14 day archiving not working either, they stays in the done column and has no where to go 😞

            Is there an update on the status of this ticket? 14 day archiving does not work. Can you please provide an option on how we can keep our projects clean? 

            Melissa Marks added a comment - Is there an update on the status of this ticket? 14 day archiving does not work. Can you please provide an option on how we can keep our projects clean? 

            The description of this ticket is a little funky. I think the thing people really want to do, certainly the thing I want to do is mark an issue as "won't do" or "duplicate" or some such. I suppose if I could just hide it I would do that and add a comment explaining why I hid it, which would be much better than my current options, but still not as nice as just marking something as closed for a particular non standard "done" reason.  

            ben.golden added a comment - The description of this ticket is a little funky. I think the thing people really want to do, certainly the thing I want to do is mark an issue as "won't do" or "duplicate" or some such. I suppose if I could just hide it I would do that and add a comment explaining why I hid it, which would be much better than my current options, but still not as nice as just marking something as closed for a particular non standard "done" reason.  

            Fell like Atlassian cares a lot of their users... By the way Jira is not free

            Evgeni Sokolov added a comment - Fell like Atlassian cares a lot of their users... By the way Jira is not free

            agreed @kpink. Disappointing. No-one from Atlassian seems bothered, we eventually stopped using Jira next gen.

            Andrzej Stempowski added a comment - agreed @kpink. Disappointing. No-one from Atlassian seems bothered, we eventually stopped using Jira next gen.

            kpink added a comment -

            almost a year and no update for basic functionality that should have been there in the first place

            kpink added a comment - almost a year and no update for basic functionality that should have been there in the first place

            is there any update on this issue?

            Peri Thompson added a comment - is there any update on this issue?

            Any progress? lack of this feature is seriously impacting us. 

            Andrzej Stempowski added a comment - Any progress? lack of this feature is seriously impacting us. 

            I think the semantics of this should be "close" rather than "hide". "Closed" is implies the issue has been dealt with explicitly whereas "hide" just implies not shown. "Closed" is not the same as "done", however, as sometimes an issue is dealt with, without actually being fixed or implemented e.g. because it is a duplicate, or it it's a bug that can't be reproduced, or it has been decided that a feature won't be implemented, or the bug can't be fixed and it is not appropriate to move the issue into "Done". 

            Jamie Bullock added a comment - I think the semantics of this should be "close" rather than "hide". "Closed" is implies the issue has been dealt with explicitly whereas "hide" just implies not shown. "Closed" is not the same as "done", however, as sometimes an issue is dealt with, without actually being fixed or implemented e.g. because it is a duplicate, or it it's a bug that can't be reproduced, or it has been decided that a feature won't be implemented, or the bug can't be fixed and it is not appropriate to move the issue into "Done". 

            The opposite would also be helpful to be able to show issues that are older than 14 days and have been resolved

            anders@sellmyhome.co.uk added a comment - The opposite would also be helpful to be able to show issues that are older than 14 days and have been resolved

            I think this issue is duplicated by 

            https://jira.atlassian.com/browse/JSWCLOUD-17257

             

            Tarun Sapra added a comment - I think this issue is duplicated by  https://jira.atlassian.com/browse/JSWCLOUD-17257  

            I think a helpful approach, if you are not using sprints, is if you mark an epic done, all the tickets in that epic that are themselves already marked Done ought to be archived immediately.

            Tim Keating added a comment - I think a helpful approach, if you are not using sprints, is if you mark an epic done, all the tickets in that epic that are themselves already marked Done ought to be archived immediately.

            iSi admin added a comment - - edited

            You say in the description that archiving issues work, but where can I do that manually now?

            iSi admin added a comment - - edited You say in the description that archiving issues work, but where can I do that manually now?

            The archive after 14 days doesn't work too. 

            Danie Kriel added a comment - The archive after 14 days doesn't work too. 

              iteong Ivan Teong (Inactive)
              aschneider@atlassian.com Adalberto Schneider
              Votes:
              119 Vote for this issue
              Watchers:
              58 Start watching this issue

                Created:
                Updated:
                Resolved: