Jira StrawberryAutomate your Jira board upkeep with an AI agent
Before standup, every ticket in the active sprint is read with its comments and its merge request. What comes back is a list of named transitions you approve or skip.
Standup at 9:15. The board says 31 issues are In Progress. Two of them shipped last Thursday, and the only real blocker is in comment eleven of a thread nobody has opened since Monday.
A companion runs the query you would have written, reads all 31 with their comments, checks the merge request in the tab you are signed into, and returns the disagreements. Each one is a named transition waiting for your sign-off.
| Job | Atlassian Intelligence | Strawberry companion |
|---|---|---|
| Summarize a long comment thread | In the issue view, no setup | Summarised alongside the PR and the email it references |
| Find why a ticket is really stuck | Works from what Jira knows | Reads Jira plus the pipeline and inbox you are signed into |
| Move 12 tickets to the right status | You click through them | Proposes each transition by name; you approve the batch |
| Turn an escalation email into a ticket | The email is outside Jira | Drafts the issue with type, priority and custom fields |
How do you make a sprint board tell the truth?
Give a companion the query you would have written and it goes past the result set.
It reads each issue with its comments, opens the merge request, and returns the four tickets whose last comment predates their status change, the two pointing at a release that already shipped, and the one assigned to somebody on leave.
Nothing moves silently. Each transition is proposed by name and you approve the ones you believe.
Write the ticket from the escalation email
Point a companion at the escalation, the incident channel or the meeting notes.
It fetches the project’s real issue types and priorities before choosing, then drafts a ticket with a reproduction path, a component, a priority and the custom fields your dashboards read.
That last part decides whether the ticket exists a week later. In most Jira sites the reporting runs on custom fields, and a ticket that skips them is invisible to every dashboard.
What can a companion answer that Jira cannot?
“Which of these 31 tickets have customers waiting” needs the support inbox.
“Did this ship” needs the pipeline. “Is this the same bug as Tuesday’s escalation” needs the email. A companion works signed in as you across all three and brings the answer back onto the ticket.
Atlassian Intelligence, as of this writing, sits in the issue view and reads the site through Atlassian’s own permissions model. The pass above is the one that needs the other three tabs to be right.
Cut the release version on Friday
A companion creates the version, gathers the issues that belong in it from a JQL query, sets the fix versions that were missed, and comments on each with what shipped. The release note usually written from memory on Monday gets written from the board on Friday.
Run it as a routine and it repeats every sprint. Teams that publish a summary outward pair it with marketing work: the same facts, rewritten for people who do not read issue keys.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents