Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • P pagerbot
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Stripe Community Contributions
  • pagerbot
  • Issues
  • #44
Closed
Open
Issue created Dec 02, 2016 by Daniel Benamy@dbenamyContributor

call_person puts previous person on call temporarily

I set up a temp service, escalation policy, and schedule for use by pagerbot. I tested it, which put me on call for 5m, and it worked. Much later, I did @pagerbot get someone_else whatever, and I got a notification from pagerduty that I was going on call, and then right after, I got the going off call notification. The incident that it created did get assigned to the someone else.

Is this a known thing?

Assignee
Assign to
Time tracking