Implement the ability for users to save custom filters applied to the approval list and definition list views.
Ensure saved filters can be managed by the user (e.g., updated or deleted).

Accepted criteria

• Users can save filters applied to the approval list view.

• Users can save filters applied to the definition list view.

• Saved filters persist between sessions.

• Users can update and delete saved filters.

Implementation details

next to the filters add a save filter button and another with a filter icon and a tooltip 'Saved filters' to display a list of saved filters.

save filter popup, add name optional description, by default private (available for the selected user). Other options available for the selected group, user, entire instance (public), conditions for groups and users can be combined.

opening the list of saved filters displays a list of available filter names with the possibility to load them

filters should be saved using the domain language. first part of the filter will be information on the selected project (if saved at project level) or projects at global level. a filter stored in project A can be used on a global level, or in project B (in this case we change the condition to project = B). a filter stored globally can be used on a project level, the condition on project IN (globally there can be many selected) is replaced by a condition on a single project

Store filters in app property

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-app-properties/#api-group-app-properties

https://developer.atlassian.com/cloud/confluence/app-properties-api/#app-properties-api