run_e648e50b558bb32f

input

{
  "request": "Triage Jira ticket MZCLD-3788: Convert GitHub bot users to GitHub Apps",
  "references": [
    "https://mozilla-hub.atlassian.net/browse/MZCLD-3788"
  ],
  "sourceContext": {
    "issue": "MZCLD-3788"
  }
}

summary

MZCLD-3788 is a Backlog ticket with no comments and no linked runbook/design doc. It asks the team to review all existing GitHub bot users and determine, for each one, whether it can be (a) converted to an outside collaborator to unblock SAML SSO enforcement on the org, or (b) converted to a GitHub App / removed to free up a paid seat license. The ticket is essentially a discovery/audit task with no acceptance criteria, owner, or inventory of bot accounts yet defined. Recommend triaging it as needing scoping: an inventory of current bot users, per-bot disposition (App vs. collaborator vs. removal), and linkage to any org SAML-enforcement epic before work can start.

findings

• Ticket is unscoped discovery work: it poses open questions rather than defining concrete tasks or acceptance criteria.
• No comments, no linked Confluence runbook or design doc, and status is still Backlog, indicating no triage or prioritization has occurred yet.
• The motivation ties to two separate outcomes: (1) unblocking SAML enforcement on the GitHub org (bot users with direct org membership can block SAML SSO rollout), and (2) reducing GitHub seat license costs by converting bots to Apps (which don't consume paid seats) or removing unused bots.
• No inventory of existing bot users is attached to the ticket, so scope/effort cannot be estimated as-is.

proposed actions

Triage note: This ticket currently reads as an open investigation rather than actionable work. To move it out of Backlog, suggest we first (1) produce an inventory of all current GitHub bot/service accounts across the org (name, purpose, repos/permissions, owning team), (2) for each, determine disposition: convert to a GitHub App (frees a paid seat, supports fine-grained permissions), convert to an outside collaborator (removes it from org membership so it won't block SAML enforcement), or deprecate/remove if unused, and (3) link this to any parent epic tracking GitHub org SAML SSO enforcement, since that appears to be the primary blocker driving this work. Once the inventory + disposition table exists, we can split this into per-bot sub-tasks or a checklist and prioritize accordingly. Flagging for scoping before further work begins.

tool calls

[
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-3788"
    },
    "result": {
      "key": "MZCLD-3788",
      "summary": "Convert GitHub bot users to GitHub Apps",
      "status": "Backlog",
      "description_text": "For all the bot users we currently have: Can a bot user be converted to an outside collaborator? This unblocks SAMLing an org. Can a bot user be converted to a GitHub App? Or removed? This frees up a license",
      "comment_count": 0,
      "comments": []
    }
  }
]

log