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

As a user, I'd like to have a global setting to disable or change the "Hide completed issues older than"from the Kanban boards

    • 1
    • 11
    • 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.

      As a user, I'd like to have a global setting to disable or change the "Hide completed issues older than" from the Kanban boards.
      It is hard to manage this option when having 100+ Kanban boards with multiple Done statuses at the workflow.

            [JSWCLOUD-20759] As a user, I'd like to have a global setting to disable or change the "Hide completed issues older than"from the Kanban boards

            Our use case: Tempo Timesheets regularly deletes worklogs as part of a data retention policy we have set. This adds issues to the board as these issues are "updated" according to Jira.

            Kalin Uzhdrin added a comment - Our use case : Tempo Timesheets regularly deletes worklogs as part of a data retention policy we have set. This adds issues to the board as these issues are "updated" according to Jira.

            i have a different scenario, where this feature completely messed up the board, because it actually shows "done and updated in last x weeks",  let me explain:

            We had a thousand of closed tickets, some of them were "Done" others "Cancelled", etc.

            Yesterday i had to bulk change more than 200 of these tickets, changing "Assignee" and/or "Reporter", i didn't changed any related to its status.

            Now i have more than 200 (and the ones that already were) in the Done Column.

            And the worst, i can't remove them from there, because i can't change the Query for Done Column.

            So, my suggestion is to change the definition of "Done" query to search for trully DONE tickets in the last x weeks (resolution date), not updated tickets AND done.

            Sandro Magrinelli Vianna added a comment - i have a different scenario, where this feature completely messed up the board, because it actually shows "done and updated in last x weeks",  let me explain: We had a thousand of closed tickets, some of them were "Done" others "Cancelled", etc. Yesterday i had to bulk change more than 200 of these tickets, changing "Assignee" and/or "Reporter", i didn't changed any related to its status. Now i have more than 200 (and the ones that already were) in the Done Column. And the worst, i can't remove them from there, because i can't change the Query for Done Column. So, my suggestion is to change the definition of "Done" query to search for trully DONE tickets in the last x weeks (resolution date), not updated tickets AND done.

            @Brendan Van Zyl - I agree with this suggestion.

            Haleigh Westwood added a comment - @Brendan Van Zyl - I agree with this suggestion.

            Even though there is a drop-dow for this as seen below....it Doesn't WORK....

            You can select any number of works....it'll still SHOW EVERYTHING.

             

            Deleted Account (Inactive) added a comment - Even though there is a drop-dow for this as seen below....it Doesn't WORK.... You can select any number of works....it'll still SHOW EVERYTHING.  

            I would add to this Suggestion to assign a different "older than" time durations for a particular issue type. For example, I want a Story that is completed only to be visible in the Done column for 2 weeks, but I want a completed Epic to be visible indefinitely.

            Brendan Van Zyl added a comment - I would add to this Suggestion to assign a different "older than" time durations for a particular issue type. For example, I want a Story that is completed only to be visible in the Done column for 2 weeks, but I want a completed Epic to be visible indefinitely.

            Hello there,

            Since not so long time I'm working with Jitra and was badly surpriced, that there are no easy and simple way to manage "hide older then..." Done stuff.

            I kindly ask wise product owners to add this feature asap. As for me this is a sufficient point to think about to change Jira to something else.

             

            Vlas Strigunenko added a comment - Hello there, Since not so long time I'm working with Jitra and was badly surpriced, that there are no easy and simple way to manage "hide older then..." Done stuff. I kindly ask wise product owners to add this feature asap. As for me this is a sufficient point to think about to change Jira to something else.  

              Unassigned Unassigned
              dbraun@atlassian.com Douglas B (Inactive)
              Votes:
              67 Vote for this issue
              Watchers:
              30 Start watching this issue

                Created:
                Updated: