Saving Preferences for UI components (Issue List) #12921

New Issue

GiteaMirror · 2025-11-02T10:25:04-06:00

GiteaMirror commented

2025-11-02 10:25:04 -06:00

Originally created by @Pontiac76 on GitHub (Apr 26, 2024).

Feature Description

MVP

The MVP for this particular request is to allow remembering what the current filters and sort order is for the currently selected repository, and have the options defaulted to "whatever" only on browser reset, cookie flush, or have you. What the user selects should be maintained for that repository when going between the issue list, and the actual issues, and then going BACK to the issue list. Storing these details in a cookie has to be easy enough. Load the details from the cookie, get the filters and order set as required, then do the required queries to the DBE through whatever means that's done.

My experience is that there is a system wide default being applied on first view and it cannot be changed to another way I want to look at the list. If I go and change the sort order, look at an issue and either hit BACK or reload the page or click the Issues list, my sort order goes to a state that "doesn't make sense" for what I needed that order for, and it's significantly irritating when going through the list in a particular order for a specific reason.

Long Term

For the long term, it'd be nice to be able to SAVE such filter+order states and have that state restored at any time, and have that state reloaded every time the user goes to that repos Issue List.

I run Gitea on my own instance, and depending on what I'm doing, per repository the ordering of the Issue List doesn't make sense for what is set as the system wide default. For that particular day, I may be looking at bugs, I may be looking at questions I've left for myself to investigate later, or I may be looking at feature requests to pick whatever I want to work on new. In one particular repository, I'm looking at an ordered list of things I need to look at, start to finish, first to last, to which is countermanded by the requirement of looking at the last submitted issue first. When I've got 300 items I want to look at, it gets tiresome to have to keep clicking the sort, or going to the last page to look at the oldest or alphabetically important item.

Being able to sort based on last updated (by any metric, comment or filter) also means I can review things I've not touched yet.

Being able to sort based on the title alone gives me the ability to go through a list alphabetically.

Being able to filter and save states on my filters will help when I want to look at only bugs, or only questions.

Screenshots

No response

Originally created by @Pontiac76 on GitHub (Apr 26, 2024). ### Feature Description ![image](https://github.com/go-gitea/gitea/assets/4532020/2ece59bc-a1a7-4569-b913-9f4a85cd205a) ### MVP The MVP for this particular request is to allow remembering what the current filters and sort order is for the currently selected repository, and have the options defaulted to "whatever" only on browser reset, cookie flush, or have you. What the user selects should be maintained for that repository when going between the issue list, and the actual issues, and then going BACK to the issue list. Storing these details in a cookie has to be easy enough. Load the details from the cookie, get the filters and order set as required, then do the required queries to the DBE through whatever means that's done. My experience is that there is a system wide default being applied on first view and it cannot be changed to another way I want to look at the list. If I go and change the sort order, look at an issue and either hit BACK or reload the page or click the Issues list, my sort order goes to a state that "doesn't make sense" for what I needed that order for, and it's significantly irritating when going through the list in a particular order for a specific reason. ### Long Term For the long term, it'd be nice to be able to SAVE such filter+order states and have that state restored at any time, and have that state reloaded every time the user goes to that repos Issue List. I run Gitea on my own instance, and depending on what I'm doing, per repository the ordering of the Issue List doesn't make sense for what is set as the system wide default. For that particular day, I may be looking at bugs, I may be looking at questions I've left for myself to investigate later, or I may be looking at feature requests to pick whatever I want to work on new. In one particular repository, I'm looking at an ordered list of things I need to look at, start to finish, first to last, to which is countermanded by the requirement of looking at the last submitted issue first. When I've got 300 items I want to look at, it gets tiresome to have to keep clicking the sort, or going to the last page to look at the oldest or alphabetically important item. Being able to sort based on last updated (by any metric, comment or filter) also means I can review things I've not touched yet. Being able to sort based on the title alone gives me the ability to go through a list alphabetically. Being able to filter and save states on my filters will help when I want to look at only bugs, or only questions. ### Screenshots _No response_

GiteaMirror added the type/proposal label 2025-11-02 10:25:04 -06:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#12921