run_965a3ebca609566e

input

{
  "request": "Triage Jira ticket MZCLD-3819: Write self-serve PagerDuty guides for engineers (notifications, being phoned while asleep, mobile app, escalation)",
  "references": [
    "https://mozilla-hub.atlassian.net/browse/MZCLD-3819"
  ],
  "sourceContext": {
    "issue": "MZCLD-3819"
  }
}

summary

MZCLD-3819 is a Backlog documentation task requesting a set of self-serve PagerDuty guides for engineers, covering notification rules, bypassing Do Not Disturb for overnight pages, mobile app setup, personal escalation paths, page response workflow, and an on-call readiness checklist. The ticket has no comments and is not yet started. It references SVCSE-2928 as the originating incident that revealed engineers with PagerDuty accounts but no working notification/escalation setup; that ticket could not be retrieved due to access policy restrictions in this run. There is no explicitly linked Confluence runbook/design doc to pull additional context from — the guides described in this ticket appear to be the deliverable themselves, not something with pre-existing documentation.

findings

• none

proposed actions

Triage note: This is a well-scoped documentation task with six clear sub-topics already outlined in the description (notification rules, DND/silent-mode bypass for iOS/Android, mobile app setup, personal escalation path, page-response workflow, and an on-call readiness checklist). Recommend: (1) confirm whether this blocks a specific upcoming announcement/invitation date mentioned in the description, and prioritize accordingly since the guides are a stated prerequisite for that communication; (2) pull relevant context from SVCSE-2928 (the migration incident that motivated this ticket) to ensure the guides directly address the failure mode observed there (accounts existing without configured escalation paths); (3) consider publishing each of the six topics as its own short Confluence sub-page under a parent 'PagerDuty Onboarding' page, ending with the 'ready for on-call' checklist as a single-page summary/gate; (4) assign an owner and target sprint given this currently sits unassigned in Backlog with no linked doc yet.

tool calls

[
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-3819"
    },
    "result": {
      "key": "MZCLD-3819",
      "summary": "Write self-serve PagerDuty guides for engineers (notifications, being phoned while asleep, mobile app, escalation)",
      "status": "Backlog",
      "description_text": "Background Having a PagerDuty account is not the same as being reachable. An engineer who has not configured their notification rules will not be woken by a page, and will not know it until an incident goes unacknowledged. SVCSE-2928 flagged exactly this during the instance migration: users needed not only to exist, but to have set up their own personal escalation path. These guides are what the announcement links to, so they need to exist before the invitation goes out. Goal An engineer who has just been given an account can get themselves properly reachable without asking anyone. Topics to cover Setting up notification rules \u2014 what to be notified by, and how quickly it escalates Getting your phone to ring while you sleep \u2014 bypassing Do Not Disturb / silent mode on iOS and Android Installing and configuring the mobile app Setting your personal escalation path What to do when you get a page: acknowledge, investigate, escalate What good looks like \u2014 a short \"you are ready for on-call\" checklist",
      "comment_count": 0,
      "comments": []
    }
  },
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "SVCSE-2928"
    },
    "result": {
      "error": "read blocked by policy: resource not in run subject",
      "args": {
        "key": "SVCSE-2928"
      }
    },
    "blocked": true
  }
]

log