Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-20229

The 'Hide completed issues older than' function for Kanban Boards should be configured to only be applied to issues in the last Column (Done Column)

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Board configuration
    • None
    • 1
    • 13
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem Definition

      As per this article, the description of the function mentions that the function applies to issues in the 'Done' column, which should be the last column. In reality, the affecting factor would be the 'Status Category'. Regardless of the Column, the issues affected by the function would be dependent on the 'Status Category' set.

      This causes some confusion in understanding the expected behavior. Also, there are some use cases where the Status with 'Done' Status Category would not be in the last Column, yet the issues would be hidden.

      Suggested Solution

      The 'Hide completed issues older than' function should only apply to the last 'Column'. Or have an additional configuration to set which Status would actually be affected by the 'Hide completed issues older than' function.

      Workaround

      If the Status is in any Columns other than the last column, set the Status Category to 'In Progress'.

            [JSWSERVER-20229] The 'Hide completed issues older than' function for Kanban Boards should be configured to only be applied to issues in the last Column (Done Column)

            tobias added a comment -

            +1 this is very misleading.

            tobias added a comment - +1 this is very misleading.

            Hello!

            Issues in column with status category "To do" in my case also get hidden, I would say not only issues from columns of status category "Done" are in scope of this functionality. That is quite misleading

            I hope you can fix this, Anna

            Anna Bartczak added a comment - Hello! Issues in column with status category "To do" in my case also get hidden, I would say not only issues from columns of status category "Done" are in scope of this functionality. That is quite misleading I hope you can fix this, Anna

            As per the feature name it should be applicable to only Done column, however if set it hides issues in all the columns based on the hiding condition. 

            Please fix the issue!

            Radha Khullar added a comment - As per the feature name it should be applicable to only Done column, however if set it hides issues in all the columns based on the hiding condition.  Please fix the issue!

            The feature should work like on a sprintboard: The last column counts.

            In most of our customer systems it is not possible to create a workflow with correct status categories. – The recommendation is always to work with generic names for objects and reuse objects – create as few new objects as possible.

            Therefore in some workflows final status (category "Done") are correctly marked and in some workflows a final status is used somewhere in the middle of the workflow, because it is reused. This means that there are sometimes kanban boards in which a status with the done category cannot be in the last column.

            There are also complex, large workflows that are split over several kanban boards for a better overview or because different departments are responsible for the workflow part. Also in this case, it does not work that "hide complete issues after ..." uses the status category.

             

            Current workaround
            Disable the feature on the board. Find a something that hides the feature after a specified time.
            Based on the solution, for example: resolution = Unresolved OR resolved >= -4w

            Detlef Steinhäuser [Communardo] added a comment - The feature should work like on a sprintboard : The last column counts. In most of our customer systems it is not possible to create a workflow with correct status categories. – The recommendation is always to work with generic names for objects and reuse objects –  create as few new objects as possible. Therefore in some workflows final status (category "Done") are correctly marked and in some workflows a final status is used somewhere in the middle of the workflow, because it is reused. This means that there are sometimes kanban boards in which a status with the done category cannot be in the last column. There are also complex, large workflows that are split over several kanban boards for a better overview or because different departments are responsible for the workflow part. Also in this case, it does not work that "hide complete issues after ..." uses the status category.   Current workaround Disable the feature on the board. Find a something that hides the feature after a specified time. Based on the solution, for example:  resolution = Unresolved OR resolved >= -4w

            I know from my customers that they use Kanban boards and many columns are included. The second last column contains issues that only need one formality and no further activity is necessary. There are filters that are used on dashboards and query the status category. In such a case it is not possible to change the status in the second last column of the status category.

            Please add this function.

            Sabine Bollwahn added a comment - I know from my customers that they use Kanban boards and many columns are included. The second last column contains issues that only need one formality and no further activity is necessary. There are filters that are used on dashboards and query the status category. In such a case it is not possible to change the status in the second last column of the status category. Please add this function.

              Unassigned Unassigned
              imazuki Irfan Mazli Mazuki (Inactive)
              Votes:
              24 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated: