run_413908f71d4a5ed6

input

{
  "request": "Triage Jira ticket MZCLD-3794: Move archived repositories to mozilla-archive organization",
  "references": [
    "https://mozilla-hub.atlassian.net/browse/MZCLD-3794"
  ],
  "sourceContext": {
    "issue": "MZCLD-3794"
  }
}

summary

MZCLD-3794 is a Backlog-status housekeeping request to relocate already-archived GitHub repositories out of active Mozilla organizations into the dedicated mozilla-archive org, reducing clutter for engineers browsing org repo lists. The ticket has no comments, no linked runbook/design doc, and lacks scoping details (which orgs, how many repos, whether via script or manual transfer, and what governance/approval is required for org-to-org repo transfers).

findings

• Ticket is a low-detail backlog item with a clear but underspecified goal: move archived repos into mozilla-archive org.
• No comments exist yet, so there is no prior triage discussion, owner assignment, or scoping decisions captured on the ticket.
• No runbook or Confluence design doc is linked in the ticket or provided in references, so process/tooling for bulk repo transfers (e.g. GitHub API script, use of an org-transfer bot, rate limits) is undocumented and needs to be established or located.
• Key open questions before work can start: which source orgs/repos qualify as 'archived' (GitHub archived flag vs. inactive), whether repo transfer preserves webhooks/branch protections/permissions, whether affected teams need advance notice, and whether this requires org admin approval or a GitHub App with transfer permissions.

proposed actions

Triage notes: This looks like a straightforward but currently underspecified cleanup task. Before moving this out of Backlog, could we nail down:

1. Scope: Which GitHub organizations should be scanned for archived repos, and do we have (or can we generate) a list/count of candidate repositories?
2. Definition: Are we targeting repos with GitHub's native 'archived' flag, or also long-inactive-but-unarchived repos?
3. Process: Do we have an existing script/tool for bulk org-to-org repo transfers (GitHub API supports repo transfer, but it requires org owner permission on both source and destination, and doesn't preserve some settings like webhooks/team access - these would need to be reconfigured or accepted as lost)?
4. Communication: Should repo owners/teams be notified before their archived repos are moved, in case of broken links or automation depending on the current org path?
5. Approval: Does moving repos between orgs require sign-off from org admins or IT/security given org-level permission changes?

Once we have an enumerated repo list and an agreed transfer method (manual vs. scripted via GitHub API/App), this can be sized and moved into a sprint. No runbook or design doc is currently linked - if one exists, please attach it here; otherwise we should draft one covering the transfer procedure and rollback plan before execution.

tool calls

[
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-3794"
    },
    "result": {
      "key": "MZCLD-3794",
      "summary": "Move archived repositories to mozilla-archive organization",
      "status": "Backlog",
      "description_text": "We have many archived repositories. We should move them to the  mozilla-archive  org so they\u2019re not cluttering up organizations people work in.",
      "comment_count": 0,
      "comments": []
    }
  }
]

log