Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • P PulsoServer
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
    • Infrastructure Registry
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Cristian Ojeda Flores
  • PulsoServer
  • Issues
  • #5

Closed
Open
Created Apr 17, 2021 by Cristian Ojeda Flores@maxMaintainer

Create new check based on previous check

This kinda breaks YAGNI, as I don’t quite need it, and no customer (lol this isn’t even public yet) has asked for it, but here it goes.

For users who want to change the hostname of a check, we allow them to create a new check with the existing check’s parameters pre-filled in the form, where they can change whatever they want.

After saving this new check, the old check is archived, and the new one displays that it was “derived from <OLD_CHECK> or something like that”.

As I say, this is merely documenting a possible idea. There’s no hurry on implementing this before the other, more critical, features.

Assignee
Assign to
Time tracking