Skip to content
getJiraIssue — drill into a specific at-risk ticket for details before drafting the updatesearch (Rovo Search, beta) — natural language query like "what's blocked in the cloud migration project" without needing to know JQLgetJsmOpsAlerts — if E7's clients use JSM Ops, the agent could pull active alerts into the briefing too (though this requires API token auth, not OAuth)
Dashboards & Gadgets — Jira dashboards can show sprint progress, issue counts by status, and blocked tickets out of the boxBurndown/Burnup charts — built-in sprint reporting shows what shipped vs. what slippedJQL saved filters — users can already save a "show me everything blocked in this project" query and view it anytimeConfluence integration — teams already use Confluence to write status reports, and Jira macros can embed live issue counts directly into a Confluence pageDraft a polished, exec-ready status update in the user's voiceInsert that content directly into an email the user is already composing in SuperhumanAdapt the tone and format based on the audience (engineering manager vs. CTO vs. client)
Example of Agent Builder in Action
When you use the “What agent to build”, make sure that you are asking about similarities or differences before you accept an agent idea.
<prompt> now think about this partner, and still think about the engineering team as the end user.
Prompt Result
Fetched: Empower Teams & Drive Digital Transformation — E7 Solutions
E7 Solutions — Atlassian Platinum Partner (multiple Partner of the Year wins) specializing in cloud migrations, JSM implementations, and managed services for mid-to-large enterprises across healthcare, legal, and tech.
Persona: Engineers and engineering managers writing in Superhuman — drafting incident comms, JSM ticket responses, migration status updates — while their work lives in Jira and Confluence.
🚨 Incident Comms Drafter
When an engineer is mid-incident and needs to send a stakeholder update fast, this agent pulls the relevant JSM ticket and drafts a clear, calm status email — severity, impact, current action, ETA — without the engineer having to context-switch out of their inbox. The user types the ticket ID or describes the incident, the agent calls the Atlassian MCP to fetch the issue details, then uses the Rewrite tool to slot a polished draft into whatever they're composing.
SDK features: addSkill, pack.addMCPServer (Atlassian MCP), ToolType.Pack, ToolType.ScreenAnnotation with ScreenAnnotationType.Rewrite, screen context.
User might say: "Draft a stakeholder update for INC-2241," "Write an incident email from this JSM ticket," "Make this sound less panicked and more professional."
📦 Migration Readiness Briefer
E7's bread and butter is cloud migrations — and migration projects generate a constant stream of status emails to IT directors and execs. This agent indexes open Jira epics and issues tagged to a migration project, then helps engineers draft weekly readiness briefs by pulling what's complete, what's at risk, and what's blocked. The user starts typing a status email, and the agent suggests a structured rewrite populated with live data from the project board.
SDK features: addSkill, pack.addMCPServer (Atlassian MCP), ToolType.Pack, ToolType.Knowledge (indexed migration epics/issues from a sync table), ToolType.ScreenAnnotation with ScreenAnnotationType.Rewrite, screen context.
User might say: "Fill in my migration status update from Jira," "What's at risk in the cloud migration this week?", "Draft an exec briefing for the STARZ migration project."
Start with: 🚨 Incident Comms Drafter. Zero indexing needed, one MCP call, and it targets the highest-stress moment in an engineer's week — writing clearly under pressure. It's also a perfect showcase pitch for E7's JSM practice specifically, since JSM is their service management anchor product. Migration Readiness Briefer is the stronger long-term story but requires the knowledge layer, making it a natural phase two.
<Prompt> Does Jira have the capability to do the migration readiness briefer?
Prompt Result
Good question — let me check what the Atlassian MCP actually exposes.
Searched the web
Yes — and it's well-supported. Here's the breakdown:
The Migration Readiness Briefer is fully achievable with the Atlassian MCP. The key tool is searchJiraIssuesUsingJql, which lets the agent query Jira with a JQL query like:
That single call can return all issues for a migration project, filtered and sorted by status (Done, In Progress, Blocked). The agent can then group them into shipped / at-risk / blocked and feed that structure into the Rewrite tool to slot it into the user's draft email.
A few other MCP tools that make it even richer:
One caveat worth knowing: JSM tools require API token auth, not OAuth — so if the agent needs to pull from JSM alongside Jira, the user's org admin needs to enable that. For a pure Jira project-based migration tracker, OAuth alone is sufficient and there's no friction.
Bottom line: the Migration Readiness Briefer is legit. The JQL search capability is exactly the right tool, and the Rovo search beta makes it even more forgiving for users who don't know their project keys.
To run code, enable code execution and file creation in Settings > Capabilities.
<Prompt> does Jira already have a feature that is similar to the migration readiness briefer?
Prompt Result
Yes, Jira does have native features that overlap — here's an honest assessment:
What Jira already does natively:
So what's the actual differentiation of the Go agent?
The gap isn't finding the data — it's writing the email. Jira can surface what's blocked, but it can't:
That's a real but narrow wedge. The honest pitch is: "Jira tells you what's happening, Go writes the email about it" — and the Rewrite annotation is what makes that feel magical vs. just copy-pasting from a dashboard.
My recommendation: If you're pitching this to E7, I'd sharpen the framing away from "migration readiness" (which sounds like a reporting feature Jira already has) and toward "stakeholder comms drafting" — the specific pain of translating Jira data into human communication for non-technical audiences. That's the gap Jira genuinely doesn't fill.
Second Agent Example
I'm meeting with my partner, , and would like two agents that they might be interested in
Does Jira have the capability to do the
does Jira already have a feature that is similar to the
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.