I ran into an interesting problem while dealing with the Jira Work Management project.
I have a board associated with my Jira Work Management project.
Problem: By Jira work management project board always shows the tickets that are already in Done state.
I know there is not sprint related to this project/board but I want to put a limit let's say I should only see the Tickets in Done column of board which were moved to done in last 7 days only.
I want to hide the older tickets in done column.
I am not sure if there is a simple way to achieve this. But any sort of workarounds are also appreciated. Thanks in advance.
Hello @badr
The board that is automatically created with a Work Management project will automatically hide tickets that have been in the done column for more than 14 days. That is not a configurable setting.
Work Management project boards do not currently have the capability for custom Quick Filters based on JQL (as is available in Agile boards created for Software projects), so that is not an option.
There is not a "simple" way to achieve this with the native functionality of the Work Management board.
If you also have the Jira Software product you could use it to make a Kanban board based on your Work Management project, and there you could configure the time period for keeping Done issues displayed. But only users with a Jira Software license would be able to see that board.
A more complicated solution would be to have a custom field in each issue that you set (via Jira Automation Rules) when an issue has been in the Done status for more than X days, and then use that field in the Work Management board Filter option. This would impact your Automation Rule Usage though, so you would have to consider that within the scope of all Automation Rule Usage for your environment.
One way to decrease the default 14-day period is to use an issue security scheme with a dedicated security level that automatically hides closed issues after a certain number of days. This can be achieved through a scheduled automation that runs once a day.
Then, after 14 days you can remove the issue security level because the JWM board will filter them by default., add the part that 'frees' those older than 14 days.
To prevent the automation from becoming overloaded, I suggest filtering to avoid touching those older than 15 days.
Scheduled trigger JQL:
Action:
IF:
Action:
Finally, this solution has the cons that it hides resolved issues for a given period for all users and throughout the system....but if this matters little in your use case, then here this may be a good workaround
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.