run_c1ec840681ef02a5

input

{
  "request": "Triage Jira ticket MZCLD-3812: Give FinOps stakeholders self-serve, persona-appropriate cost reporting and showbacks",
  "references": [
    "https://mozilla-hub.atlassian.net/browse/MZCLD-3812"
  ],
  "sourceContext": {
    "issue": "MZCLD-3812"
  }
}

summary

MZCLD-3812 is a placeholder/reservation epic (status: Backlog, no comments yet) capturing two long-standing FinOps commitments — persona-appropriate self-serve cost reporting and recurring showbacks — that have never had a durable implementation. The ticket explicitly states 2027 scope is undefined and lists open questions that must be resolved before it can be split into real scoped epics. Attempts to read related tickets (MZCLD-3503, MZCLD-1811, MZCLD-3421, MZCLD-3730) for corroborating context were blocked by tool/policy scope restrictions limiting access to only MZCLD-3812, so this triage relies solely on the ticket's own description.

findings

• The ticket is explicitly a placeholder with no defined 2027 scope, no acceptance criteria, and no T-shirt size — it exists only to reserve a backlog slot between FY26 theme wind-down and 2027 planning.
• There is significant risk of duplicated or wasted effort: a prior attempt at the persona-dashboard half of this work (MZCLD-1811) was cancelled, and a currently active effort (MZCLD-3503, Cloud Cost and Usage MCP server) may already satisfy the self-serve/persona-appropriate goal, making a separate report build redundant.
• The showback capability may have an upstream dependency on cost-classification work that has not been confirmed to have landed, which could block scoping if not resolved first.
• Showback (informational cost visibility) and chargeback (actual cost allocation/billing) are explicitly called out as very different in organizational cost and complexity, and the ticket has not yet decided which is in scope — this is a major scope-defining decision that should be resolved before any estimation.
• A candidate delivery mechanism for showbacks already exists informally (consumption emails to engineering-manager workgroups) but is only a noted idea in another placeholder ticket, not a committed design.
• This triage agent's read access was restricted to MZCLD-3812 only; attempts to pull the referenced related tickets (MZCLD-3503, MZCLD-1811, MZCLD-3421, MZCLD-3730) for corroborating detail were blocked by policy, so cross-ticket verification could not be performed.

proposed actions

tool calls

[
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-3812"
    },
    "result": {
      "key": "MZCLD-3812",
      "summary": "Give FinOps stakeholders self-serve, persona-appropriate cost reporting and showbacks",
      "status": "Backlog",
      "description_text": "Background FinOps reporting today is one-size-fits-all: the consolidated cost dataset in BigQuery plus dashboards, read the same way by everyone. But the people who need cost answers aren't one audience \u2014 Finance needs actuals vs budget and accrual-ready figures, engineering managers need their own team's consumption, service owners need per- app_code  detail, leadership needs trend and forecast. Today each is served by a FinOps person hand-cutting a view or answering the question directly. Showback \u2014 telling a cost owner what their spend was, without moving money \u2014 was an OKR commitment as far back as IOKR25-46 (\"metering and showbacks for top 20 cloud cost contributors\") and still has no durable implementation. Prior art worth heeding:  MZCLD-1811 (Google SoW, \"Implement Finance Persona Dashboard\") attempted the persona half of this and was  cancelled . MZCLD-3503 (Cloud Cost and Usage MCP server) is the current live attempt at self-serve cost answers for both engineers and non-technical staff \u2014 it may make separate persona reports unnecessary, or may be the surface they're delivered on. Goal Cost owners and Finance can get the cost view appropriate to their role without a FinOps person assembling it, and MozCloud can issue recurring showbacks to cost owners. Placeholder \u2014 scope TBD 2027 scope is not defined. This epic reserves the slot so these two capabilities aren't lost between the FY26 theme winding down and 2027 planning starting. Splitting into real scoped epics is part of 2027 planning. Open questions to resolve before scoping: Which personas are genuinely distinct enough to justify separate reporting (Finance / engineering manager / service owner / leadership)? Does MZCLD-3503's MCP server already satisfy \"self-serve, persona-appropriate\" and make separate report builds redundant? Showback delivery mechanism \u2014 the \"consumption emails to engineering-manager workgroups\" commitment noted in MZCLD-3730 is the closest existing idea. Showback only, or a path to chargeback? Very different organizational cost. (FY26 chargeback process work exists in MZCLD-1569; chargeback is not showback.) Does showback depend on the  app_code  to P&L classification work in MZCLD-3421 landing first? Done when 2027 scope is written down, the persona list and showback mechanism are decided, the overlap with MZCLD-3503 is resolved, and this placeholder is either replaced by real scoped epics or rewritten with its own acceptance criteria and T-shirt size. Related MZCLD-3503 \u2014 Cloud Cost and Usage MCP server; likely delivery surface / possible overlap MZCLD-1811 \u2014 Finance Persona Dashboard (Cancelled); prior attempt MZCLD-3421 \u2014  app_code  to P&L (COGS) classification; likely showback prerequisite MZCLD-3730 \u2014 FinOps Q4 2026 placeholder; source of the consumption-email idea MZCLD-3733 \u2014 non-cloud AI vendor costs; feeds the same dataset Part of theme:  MZCLD-955 (FinOps: Cloud Cost Visibility FY26)",
      "comment_count": 0,
      "comments": []
    }
  },
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-3503"
    },
    "result": {
      "error": "read blocked by policy: resource not in run subject",
      "args": {
        "key": "MZCLD-3503"
      }
    },
    "blocked": true
  },
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-1811"
    },
    "result": {
      "error": "read blocked by policy: resource not in run subject",
      "args": {
        "key": "MZCLD-1811"
      }
    },
    "blocked": true
  },
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-3421"
    },
    "result": {
      "error": "read blocked by policy: resource not in run subject",
      "args": {
        "key": "MZCLD-3421"
      }
    },
    "blocked": true
  },
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-3730"
    },
    "result": {
      "error": "read blocked by policy: resource not in run subject",
      "args": {
        "key": "MZCLD-3730"
      }
    },
    "blocked": true
  }
]

log