Notifications page: add a filter by unread status #239
Labels
No Label
Priority
Critical
Priority
High
Priority
Low
Priority
Normal
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Type
Breaking
Type
Documentation
Type
Enhancement
Type
Feature
Type
Report
Type
Security
Type
Suggestion
Type
Testing
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/extensions-website#239
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
From chat:
This can be accomplished by a simple filter that would toggle between "all", "read" and "unread" notifications.
@pablovazquez @martonlente any thoughts on this UX? I thought that it may be also possible to have just "read" and "unread" or "all" and "unread", but maybe there is an argument to have all three?
What do you think?
@Oleg-Komarov I think a simple button row with All, Read and Unread items could work, similarily to what we do in blender-studio to filter notifications. I mean something like this:
Optionally we could also icons to make Read and Unread buttons more noticable.
Deployed in production.