🔖 Feature description
Currently, the Tracker dashboard persists filters and GitHub authentication credentials across page refreshes using browser storage.
However, users do not have an easy way to:
- reset saved filters
- clear persisted search states
- remove stored session/authentication data
without manually clearing browser storage.
✅ Proposed Solution
Add dedicated UI actions for:
1. Reset Filters
This should clear:
- active tabs
- search queries
- issue/PR filters
- pagination state
- selected repository
- date ranges
and restore the dashboard to its default state.
2. Clear Persisted Session / Logout
This should:
- remove stored GitHub credentials from sessionStorage
- reset authentication state
- safely redirect or refresh the tracker state
🎯 Expected Benefits
- Improved user experience
- Easier session management
- Better control over persisted dashboard state
- Cleaner UX for shared/public systems
📂 Possible Implementation Areas
src/pages/Tracker/Tracker.tsx
src/hooks/useGitHubAuth.ts
- persistence utility logic
🎤 Screenshot
No response
🔄️ Additional Information
This feature would complement the recently implemented persistence functionality and provide a complete session management experience for users.
The implementation can remain lightweight by reusing existing state setters and browser storage cleanup logic.
🔖 Feature description
Currently, the Tracker dashboard persists filters and GitHub authentication credentials across page refreshes using browser storage.
However, users do not have an easy way to:
without manually clearing browser storage.
✅ Proposed Solution
Add dedicated UI actions for:
1. Reset Filters
This should clear:
and restore the dashboard to its default state.
2. Clear Persisted Session / Logout
This should:
🎯 Expected Benefits
📂 Possible Implementation Areas
src/pages/Tracker/Tracker.tsxsrc/hooks/useGitHubAuth.ts🎤 Screenshot
No response
🔄️ Additional Information
This feature would complement the recently implemented persistence functionality and provide a complete session management experience for users.
The implementation can remain lightweight by reusing existing state setters and browser storage cleanup logic.