Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.web beat.web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.webbeat.web
  • Issues
  • #288
Closed
Open
Issue created Sep 04, 2015 by André Anjos@andre.anjos💬Owner

Notification upon "New environment" or "New database version"

To include in the feature list for the notification framework (besides #230 (closed) and #227 (closed)):

  • If a new database version is released by the system administrators, it should signal a search for all experiments using the previous version and notify the relevant user a newer version of the database is available (with a link to the new database page).
  • If a new version of an environment is released, then we should do the same, i.e., scan all experiments that use that environment and notify users of the new environment (with a link to the new environment description).
Assignee
Assign to
Time tracking