Blog · 28 September 2026

Jira weekly report: the filter, the email, and the ticket

A Jira weekly report usually comes down to two pieces. The first is the data: a saved JQL filter for what was created, resolved and still open in the last seven days, emailed to the team every Monday through a filter subscription. The second is the ritual: somebody has to read that list and write the few sentences a manager or a client actually wants. Jira Cloud gives you the first piece for free. The second piece is a job that comes back every week, and the tidy way to handle it is a status report ticket that appears in the backlog on schedule, with an owner and a due date.

This guide builds both. Statements about Jira's built-in features are as of September 2026, from Atlassian's own documentation.

What people mean by a Jira weekly report #

The phrase covers a few different reports, and it pays to decide which one you are producing before you build anything.

The status report is the one Jira cannot write for you. Every other row is a query. The status report is a judgement about the queries, which is why teams that skip the ritual end up with a lot of emails and no report.

Step 1: write the queries #

A weekly report needs three or four saved filters. Open the issue search, switch to JQL, and save each one with a name that says what it is.

1. Resolved this week: project = OPS AND resolved >= -7d ORDER BY resolved DESC
2. Created this week: project = OPS AND created >= -7d ORDER BY created DESC
3. Still open and overdue: project = OPS AND due < now() AND statusCategory != Done
4. Blocked or stuck: project = OPS AND status = Blocked or, if you have no such status, project = OPS AND statusCategory = "In Progress" AND updated <= -5d

Replace OPS with your project key. The relative dates (-7d, -5d) are what make the filters reusable: the same query is correct every week without anyone editing it.

If your week runs Monday to Sunday rather than "the last seven days", use startOfWeek() instead: resolved >= startOfWeek(-1w) AND resolved < startOfWeek() gives last calendar week. Which start day counts as the start of the week depends on your Jira locale settings, so check one result against a calendar before trusting it.

Step 2: email the numbers with a filter subscription #

A filter subscription is the built-in way to have Jira send a report on a schedule. Atlassian describes it like this:

Subscribing to a filter provides you with a periodic notification for all work items returned by the search.

Setting it up #

1. Run the saved filter.
2. Select Details next to the filter name, then New subscription.
3. Choose the recipients: yourself, or a group you belong to.
4. Pick the schedule. Weekly on Monday morning is the usual choice for a weekly report. Use Advanced if you need a cron expression; our Jira cron expression guide covers the syntax.
5. Save, and repeat for each filter you want in the report.

What to know about subscriptions #

• Only the first 200 results are sent, according to Atlassian's page. For a busy project, "created this week" can exceed that without anyone noticing, so narrow the query or split it by component.
• It sends a list, never a summary. The email is the raw data. No one is told what it means.
• Group subscriptions need a global permission (Manage Group Filter Subscriptions), so a team lead without it can subscribe only themselves.

For a team that just wants to see what moved, this is the whole report and you can stop here.

Step 3: use the sprint report if you run Scrum #

If the team works in sprints, the sprint report already does much of the weekly job. In Atlassian's words:

The sprint report shows the list of work items in each sprint. It's useful for your Sprint Retrospective meetings, and also for mid-sprint progress checks.

Two limits worth knowing before you lean on it. It only applies to Scrum boards, and Atlassian notes that estimates on subtasks are not included in it, only estimates on parent work items. On a one-week sprint the sprint report is effectively your weekly report. On a two-week sprint it is a mid-point check for the week in between, and our sprint planning guide covers the meeting at the other end of it.

Step 4: put the weekly status report on the board #

The numbers arrive by email. The written status report still depends on one person remembering, every single week, to open the filters and write it. That is the part that slips first: a busy week, a holiday, a handover, and the report quietly stops.

The fix is to treat the status report as what it is, a recurring piece of work, and give it a ticket. A ticket has an assignee, a due date and a place to put the text, and an unfinished one shows up in the same views as every other late item.

Three ways to create the ticket each week #

Cloning by hand works for a while and fails exactly when the team is busiest. A Jira Automation rule with a Scheduled trigger and a Create work item action is the native option; Atlassian's trigger reference, as of September 2026, says you can "run the flow at a fixed rate (for example, every 7 days), or use a Cron expression for more complex schedules." Each run counts toward your plan's monthly usage, which we cover in Jira Automation pricing, and Atlassian also states that "Scheduled flows that reach a Failure status for 10 consecutive executions will disable automatically."

How it looks in Recurring Work Items for Jira #

Recurring Work Items for Jira is our app, and a weekly report ticket is a typical first rule.

1. Turn the app on for the project and choose who may schedule.
2. Create a rule that repeats on chosen weekdays, for example every Friday.
3. Write the summary with tokens so each week's ticket has its own name, for example Weekly status report {{now.date}}. A token that is misspelled is refused when you press Save, so you do not discover the typo in a ticket title weeks later.
4. Put the report outline in the description: links to the saved filters from Step 1, and headings for Done, Next, Risks.
5. Set the assignee, and the due date as an offset from the run, such as the same day.

Because it runs on its own Forge scheduler, it uses no Jira Automation quota, and every run, whether it created, skipped or failed, is written to the rule's history. It is scoped to one project, so the weekly report rule for the operations team never creates tickets in anyone else's project. It is free for up to 10 users.

A template for the report itself #

Whatever creates the ticket, the report is easier to write when the description already holds the outline. A version that works for most teams:

• Done this week: three to five lines, taken from the Resolved this week filter. Outcomes, not ticket numbers.
• Planned for next week: what the team will pick up, and anything waiting on someone outside it.
• Risks and blockers: everything from the Blocked or stuck and Overdue filters that a reader should act on.
• Asks: decisions or help needed, each with a name.

Keep it short enough to write in fifteen minutes. A report that takes an afternoon is the one that stops being written. The filters carry the detail; the report carries the meaning.

If the same checklist of steps goes into every report, see where checklist steps should live, and for turning a ticket into a reusable starting point, Jira task template.

When the manual way is enough #

You do not need an app or a rule for this if:

• The report is only for the team. A subscription on two or three filters is the report, and nobody needs to write prose about it.
• One person writes it and never misses. A recurring calendar entry costs nothing and may be all the reminder they need; our Jira reminder guide covers the other options.
• You run one-week sprints. The sprint report plus a short comment in the retrospective does the job.

A scheduled ticket earns its place when the report goes to people outside the team, when the writer rotates, or when a missed week is noticed by a client before it is noticed by you.

Frequently asked #

Can Jira email a weekly report automatically? Yes. Save a JQL filter and add a filter subscription with a weekly schedule. The email lists the matching issues, up to the first 200.

How do I get last week's resolved issues in Jira? Use resolved >= -7d for the last seven days, or resolved >= startOfWeek(-1w) AND resolved < startOfWeek() for the previous calendar week.

Can Jira create a weekly status report ticket every week? Yes, with a Jira Automation rule on a Scheduled trigger, or with a scheduling app such as Recurring Work Items for Jira, which creates the ticket on the day you choose with its own title and due date.

Want the weekly report ticket to show up on its own? Install Recurring Work Items for Jira and write the rule once.