Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
G
gracedb
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 100
    • Issues 100
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1
    • Merge Requests 1
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lscsoft
  • gracedb
  • Issues
  • #183

Closed
Open
Created Nov 17, 2019 by Nicolas Arnaud@nicolas.arnaud

Pause button for the notifications in https://gracedb.ligo.org/alerts/

Description of feature request

It would be great if there were a "Pause" button in the "Notifications" section of https://gracedb.ligo.org/alerts/ in addition to "Edit" and "Delete". Currently to deactivate a notification one has to delete it. Setting it to "pause" would allow to keep it deactivated for a while. That would ease the re-enabling of that notification at a later time.

Use cases

Debug/test/engineering run notifications that one would like to only keep active for a given time period but that could be activated again at a later time. People on rota may want to have particular notifications enabled only when they are on duty.

Benefits

No need to set notification(s) again, with the risk to make typos. Have examples of notifications that worked in the past and could be reused, either as such or slightly modified.

Drawbacks

People could click the "Pause" button by mistake or forget it had been set for a given notification. So clicking on "Pause" should trigger an "Are you sure?" popup and deactivated notifications should be clearly identified on the Alerts GraceDB page: different font/color/etc.

Suggested solutions

Condition blocks to be added to the existing code!?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None