As a Freshrelease user, I would like to have the ability to set a default custom filter for a project so I don't have to select this item filter every time after clicking on the "items" menu button.
We currently use multiple filters per Kanban project. Currently, the behavior of the default filter differs per project and seems to be random. Some projects open the "All items" filter, others a custom one.
Hi Sjaak Overgaauw,
Thank you for the details you have shared. In our current implementation, the Last Viewed Filter will be remembered inside a project. If you view 'Items - Open' filter in Project A > Go to other modules / close the browser and then visit the All Items tab again, you will see the same view.
However, if you change to All Items tab in another project (say Project B) , since this New project will not have the afore mentioned filter, the view will reset to the 'All Items' filter.
- Prathees R (Freshrelease Team)
The fact that the view/filter is reset to "All items" is exactly what Freshrelease users don't like. We are an IT consultancy business, we have 1 project setup per customer. Most developers work for multiple customers at the same time. We use Kanban only, not Scrum. The "Items - open only" view is, therefore, the most used one since it filters the "done" ones as long as they aren't released yet.
In addition to that, the all items board contains items of all item types both Epics, Tasks and sub-tasks. It's currently not possible to save and overwrite the filter of the "All items" and to rename it. That would also be a solution. But anyway, due to different workflows and status columns, it's not handy to show both Epics and tasks on 1 single-board when using Kanban.
So, hence our proposal for a default board option, which is opened if you click on the items button.
Hi Sjaak Overgaauw,
// We are an IT consultancy business, we have 1 project setup per customer. Most developers work for multiple customers at the same time.
We understand the use-case and will put our best efforts to address this in better ways. In our current implementation, the Last Viewed filter is remembered without the project context and hence we couldn't resolve this immediately.
On a related note, in one of the features (Columns Customisation in List Views) that we are working now, we are planning to support the User Personalisation in the context of a Project. When this ready, we hope to extend that to the viewed filters also. We will keep this thread posted about the updates.