run_1952d208b45d85c2

input

{
  "request": "Triage Jira ticket MZCLD-3844: Archive inactive organizations",
  "references": [
    "https://mozilla-hub.atlassian.net/browse/MZCLD-3844"
  ],
  "sourceContext": {
    "issue": "MZCLD-3844"
  }
}

summary

MZCLD-3844 "Archive inactive organizations" is a Backlog ticket with a very sparse description ("My educated guess on organizations we should archive:") and no comments. The description appears truncated/incomplete — it likely originally included a list or table of candidate organizations that isn't showing up in the plain-text extraction (e.g., an attachment, embedded table, or panel). There is no linked runbook or Confluence design doc referenced in the ticket to pull additional context from. Before this can be actioned, we need the actual list of organizations, the definition/criteria for "inactive," and confirmation of what "archive" means operationally (data retention, reversibility, notification to org admins, etc.).

findings

• Ticket description is incomplete — it ends mid-sentence with no actual list of organizations or criteria attached in the plain-text body.
• No comments exist on the ticket, so there is no additional discussion, criteria definition, or stakeholder sign-off recorded.
• No linked Confluence runbook or design doc was found in the ticket content to clarify the archival process, criteria for 'inactive', or rollback/reversal procedure.
• Ticket remains in Backlog status, consistent with it being an initial/unrefined idea rather than a scoped, actionable task.

proposed actions

Thanks for filing this. Before we can triage/action this ticket, we need a bit more detail since the current description appears cut off:

1. Could you attach or paste the actual list of organizations you believe are inactive (the description currently ends at "My educated guess on organizations we should archive:" with no list visible)?
2. What criteria define "inactive" (e.g., no logins/API calls for N days, no active subscriptions, no members, etc.)? Is there a query or dashboard we can reference/automate against?
3. What does "archive" mean operationally here — soft-delete/flag, data retention period, is it reversible, and do org admins/users get notified beforehand?
4. Is there an existing runbook or design doc for org lifecycle/archival we should follow? If so please link it.

Once we have the org list and criteria, we can scope this into an actionable task (and consider whether it should be a recurring/automated job rather than a one-off).

tool calls

[
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-3844"
    },
    "result": {
      "key": "MZCLD-3844",
      "summary": "Archive inactive organizations",
      "status": "Backlog",
      "description_text": "My educated guess on organizations we should archive:",
      "comment_count": 0,
      "comments": []
    }
  }
]

log