-
Suggestion
-
Resolution: Unresolved
-
295
-
61
-
Issue Summary
Issues in the Done status are not being removed from the Kanban boards after the set amount of weeks passed.
Hide completed issues older than function should hide issues whose Resolution Date are older than the selection supplied by the user without considering if the Issue was updated after that date.
Steps to Reproduce
- Step 1 - Create an Issue and set it to Done status.
- Step 2 - After one to four weeks depending on the board settings, it will disappear.
- Step 3 - Edit and do a change on the issue.
Expected Results
In the General and filter board settings the Hide completed issues older than feature should consider the date in the Resolved field.
Actual Results
In the General and filter board settings the Hide completed issues older than feature considers the date in the Updated field. This means that if an issue is Resolved and then later edited, it will reappear on the Kanban board.
Workaround
Do not edit an Issue once set to Done status.
OR
Edit your board filter so that it excludes tickets that were Resolved more than 2 weeks ago:
project = CMK AND (resolved >= -2w or resolved IS EMPTY) ORDER BY Rank ASC
- is duplicated by
-
- Closed
- relates to
-
- Gathering Interest
- resolves
-
- Closed
- is related to
-
ENT-2641 Failed to load
[JRACLOUD-86404] "Hide completed issues older than" on Kanban Boards should consider Resolution Date
Any update on this? The current behavior is not intuitive at all - and doing bulk changes on project boards becomes a headache as a result of this bug.
I completed agree that the current behaviour is misleading. I expected that this feature is based on when an issue got completed and not when it was last updated.
This affects on our team as well when we tried to update the workflow statuses on a certain issue type. After publishing the workflow and associating the old statuses to the new statuses, OLD tickets started to show up on the Kanban board, even if those tickets are already resolved/closed last year. Now, we are just waiting for a week to pass before they be removed on the board.
Yeah, it's crazy the hoops you have to jump through in order to work around this "feechur". I just solved it with some fancy JQL, but this doesn't make any sense; basing the expiration from the Done on Updated rather than Resolved might make sense in a few cases, but none in my organization.
Another "interesting" case occurs when you update the workflow for more than 4000 issues in a given project:
On mapping the old status name with the new status name, the updated date of thousands of issues changed, causing the board not to be able to load with an error message indicating there were too many issues and suggesting to update the board filter to fix it...
This is an obvious feature, it is intuitively embedded in the understanding of ticket management. Please implement it.