Internal copilot filed an executive-priority Jira ticket against the wrong project
A $4B B2B SaaS company's internal AI assistant created a Jira ticket against the wrong product line during a board-week prep cycle. The PM caught it 28 hours later.
Wrong tool, wrong arguments, right credentials. The copilot did what it was permitted to do, not what the operator intended.
Key facts
- What
- A $4B B2B SaaS company's internal AI assistant created a Jira ticket against the wrong product line during a board-week prep cycle.
- Incident date
- Sep 22, 2025
- Who
- Anonymized: B2B SaaS · NA · $4B+ revenue
- Failure mode
- Tool Misuse
- AI surface
- Copilot
- Severity
- Medium
What happened
An internal Atlassian-integrated copilot at a $4B-revenue B2B SaaS company created a high-priority Jira ticket during a board-prep week and routed it to the wrong product team. The ticket sat with the wrong owner for 28 hours and triggered a re-prioritization of the wrong sprint. The product manager caught the misroute when the wrong team began work on a problem they did not own.
Realm Labs reconstructed the mechanism with the customer under NDA. The incident is anonymized at the customer's request.
The headline of this case is that an AI failure does not need to be public, or large, or visible to cost the operator. It needs to land in the wrong row in a system of record.
What broke inside the model
- 01 · TriggerThe agent selects the correct tool.
- 02 · Model stepIt fills the call with the wrong arguments.
- 03 · Control gapNo validation checks the arguments first.
- 04 · FailureThe tool runs against the wrong target.
- 05 · ConsequenceThe wrong record, account, or system is hit.
At the tool call, the arguments point at the wrong target.
Tool misuse. The copilot picked the right function (create Jira ticket) and passed the wrong arguments (wrong project key). The copilot's reasoning had identified the problem correctly. The slot filling for "which project" was wrong. The copilot did what it was permitted to do.
What it cost
Lost engineering sprint, board-week trust loss
Sources
- Customer-DisclosedRealm Labs case file under NDAfailureindex.ai
Cite this entry
https://failureindex.ai/failures/anonymized-vp-saas-jira-ticket-wrong-projectAI Failure Index. "Internal copilot filed an executive-priority Jira ticket against the wrong project" (FI-0019). Realm Labs. https://failureindex.ai/failures/anonymized-vp-saas-jira-ticket-wrong-project (indexed May 13, 2026).Data fields CC-BY 4.0, prose citation permitted. Incident ID FI-0019. Full dataset at /data.
Note from Realm Labs, the Index steward
How Realm would have caught this
- OmniGuard
- AgentRealm
AgentRealm inspects each tool call against the agent's stated intent and the operator's policy. A high-priority Jira ticket routed to a project the copilot's user does not own fails the policy check. The ticket either gets re-routed to the correct project at runtime, or the copilot is prompted to confirm the project key with the user. The 28-hour misroute does not happen.