Skip to content

[ Suggestion ] Improved notification management #12

Description

@AnthonyPoschen

Currently when you have many notifications due to agents doing lots and lots you might want to mark all as read for your personal repositories but you have to check all notifications are in fact for that, currently it isn't possible to cursory check in plugin if all notifications are for the same specific repo's you currently want to ignore because you know what the agents are doing. So you end up spam left clicking the "tick" to accept them until you can see all the remaining notifications. Ironically once it isn't a overflowed list the mark all read goes away so you have to keep clicking them, so i have some suggestions for ux

  1. Make the tick next to the notification on the right more prominant as an action ( took me a while to realise it was clickable ) im thinking maybe slighty different background color on the button so you spot the button visually for new users
  2. Make it easier to click, its a tiny box floating, no reason why the click box cant take full vertical and remaining horizontal to the back of the row.
  3. add an up and down arrow that is together to paginate through notifications on the bottom action row ( might be worth doing this for other sections too for consistency )
  4. let the mark all read button always be visible when notifications > 0

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions