Write me a weekly status update from this week's Jira tickets
Pull the week's resolved and still-moving tickets with two JQL filters, then write a short headline, a status, wins, blockers and next steps.
Smalt AI team ·
Pull two lists from Jira: tickets resolved in the last seven days and open tickets updated in that time. Write a one-to-three-sentence headline with a status of On Track, At Risk or Off Track, then add wins, what needs input, and what is next. Send it at the end of the week, in the project tool or the team channel.
Pull the tickets, then write the update
Get this week’s tickets with two filters
A status update is only as accurate as the list behind it, so start with a saved Jira filter and not your memory of the week. Below are two JQL queries as examples to adapt. Replace OPS with your project key, and check how the resolved and updated fields behave in your own Jira before you trust the counts.
Done this week:
project = OPS AND resolved >= "-7d" ORDER BY resolved DESC
Still moving:
project = OPS AND statusCategory != Done AND updated >= "-7d"
The relative dates work because Jira accepts an increment in the form (+/-)nn followed by y, M, w, d, h or m. Atlassian’s JQL functions reference gives created > startOfDay("-3d") as its example and says a plus is assumed when you leave the sign off. That page documents Jira Software Server and Data Center 10.0, not Cloud, so confirm the syntax against the version you run. If you want a calendar week and not a rolling seven days, the same page lists startOfWeek, which takes the same kind of increment.
Atlassian also has a knowledge base article on a weekly filter subscription. Its pattern is project = "PROJECT_KEY" AND created >= "-1w" ORDER BY created DESC. The steps, which you can repeat for each of your two queries:
- Go to Filters, then Search work items, and switch to JQL.
- Enter the query and save it as a named filter.
- Open the filter details and choose Add Subscription.
- Pick the recipients and set the schedule to weekly.
- Select Subscribe.
A subscription emails you the list on schedule, which is a good prompt to write the update. It does not write the update for you.
Choose the sections
Atlassian’s weekly project updates play is a useful skeleton. It suggests a status of On Track, At Risk or Off Track, plus any due-date change and the reason for it. Below the status it lists these sections:
- Wins: the high-level results, not every ticket.
- Needs input: blockers or open questions.
- Focus: what is next.
- Decisions: with the rationale.
- Risks and Learnings.
Atlassian recommends a short headline of one to three sentences, with the deeper sections optional, and tags for the people whose feedback you need. Its suggested rhythm is once a week at the end of the week, with a Friday block as one option.
Your “done this week” filter feeds Wins. Group tickets by outcome and name the outcome (“refund checklist rewritten and in use”) with the ticket keys in brackets, not a list of titles. Your “still moving” filter feeds Focus and Needs input: anything stuck on another person goes under Needs input with that person tagged.
If the update goes to your own team and not stakeholders, Atlassian’s weekly team updates play offers a Weekly Wrap. It lists achievements, each tied to its impact, plus team recognition. Its Week-Ahead version asks for the top three priorities with the reason for each, and challenges paired with the help you need. For the message itself it suggests a short greeting, the update, and an invitation to ask questions.
Post it where people will see it
Atlassian’s advice is to post in the project tool, and also in the team channel if the two are not integrated. Keep the same headline in both places so nobody reads two versions.
Doing it with an AI coworker
If your tickets live in Jira, connect Jira to Smalt and ask it to draft the update from the tickets you point it at: “Write this week’s status update from the tickets in these two OPS filters, with wins, needs input and next week’s priorities.” Check the draft against your own filter results before you send it. You can ask for it to be saved as a Notion page, and for a short version to be posted to your team’s Slack channel. Slack messages wait for your approval to send, so you can edit the wording first. Notion pages do not wait, so ask for the draft in a page you are happy to see created. Smalt can only post to Slack, so it has no view of what your team said there, and anything decided in a conversation, including blockers, needs to be pasted in.
What to check before you rely on it
Read the status line yourself. A filter can tell you that nine tickets closed; it cannot tell you whether the project is On Track or At Risk. That is a judgement about the due date, and it is yours to make.
Check the filters against reality once. Tickets can be resolved without being finished, reopened later, or closed in bulk during a clean-up, and any of these will inflate the “done” list. Tickets that moved only because someone changed a label will show up as updated. Skim the list and drop the noise before you summarise it.
Count what is missing. Work that never had a ticket, such as a conversation that unblocked a vendor, will not appear in any query. If it mattered, add it by hand.
Watch for ticket titles that mean nothing to the reader. Stakeholders do not need keys, they need outcomes, so translate before you send.
Finally, confirm the JQL against your version. The reference cited above is for Server and Data Center 10.0, and the saved-filter steps are written for the current Jira interface. Menu names and function behaviour may differ on your instance. We found no published statistics on how much time a weekly update saves, so judge the benefit by whether your readers stop asking you what happened.
Smalt is an AI coworker that takes jobs like this end to end and hands back the finished file.