Blog ·

Jira monthly report: the filters, the email, and the ticket on the 1st

A Jira monthly report comes down to three parts: a few saved filters that answer "what happened last month", a delivery that puts those results in front of people on a schedule, and a person who turns the results into a short summary. Jira handles the first two well with JQL date functions and filter subscriptions. The third part is the one that slips, because nothing in Jira asks anybody to write the summary. This guide covers the JQL for a calendar month, how to email it, an outline for the report itself, and how to make the "write the monthly report" ticket appear on the first working day of every month.

Statements about Jira's own features are as of October 2026, read from Atlassian's support documentation. Check your own site before relying on a detail, since Atlassian changes the product often.

What a monthly report should answer #

A weekly report is about momentum. A monthly report is read by people further from the work, so it answers bigger questions:

If the team already writes a weekly status, the monthly report is not four weekly reports stapled together. Our Jira weekly report guide covers the weekly rhythm; the monthly one is shorter on detail and longer on direction.

Step 1: JQL for last month #

The calendar month is where most monthly reports go wrong. created >= -30d gives a rolling thirty days that never lines up with the month a finance or leadership reader thinks in. Use the month functions instead.

Atlassian's JQL reference describes startOfMonth() as a function to "Perform searches based on the start of the current month", and gives an increment syntax with this example:

Find new work items created since the start of last month: created > startOfMonth("-1")

That example includes the current month too. For last month only, bound it on both sides:

Filter JQL
Resolved last month project = OPS AND resolved >= startOfMonth(-1) AND resolved < startOfMonth()
Created last month project = OPS AND created >= startOfMonth(-1) AND created < startOfMonth()
Overdue right now project = OPS AND due < now() AND statusCategory != Done
Open and not touched in 30 days project = OPS AND statusCategory != Done AND updated <= -30d

Save each one as a filter with a clear name, such as OPS: resolved last month. Because the dates are relative, the same filter answers correctly every month without editing. If you want month to date instead, drop the upper bound: resolved >= startOfMonth().

Two details worth knowing:

Step 2: Get the numbers delivered #

You have two native ways to see the results on a schedule.

A filter subscription. Atlassian's filter documentation says subscribing "provides you with a periodic notification for all work items returned by the search", and that "You can create a subscription of any frequency for yourself and/or other users." Open the filter, select Details, then New subscriptions, and pick a monthly schedule. One limit matters for a monthly report: "only the first 200 results of a filter are sent." A busy project can pass that in a month, so subscribe to the narrow filters (overdue, stuck) and look at the big ones on a dashboard.

A dashboard. Put the four filters on one dashboard with a Created vs. Resolved chart and a two-dimensional filter statistics gadget grouped by assignee or component. Readers can open it whenever they like, and the report can link to it rather than paste tables. Our Jira dashboard examples show layouts that work for this.

Either way, the numbers arrive. What does not arrive is the paragraph that says what they mean.

Step 3: The report outline #

Put this outline in the description of the monthly report ticket, so the writer starts from structure instead of a blank page:

  1. Summary in three sentences. The month in plain words, for someone who reads nothing else.
  2. Delivered. Three to six outcomes, each linked to its epic or issue.
  3. Intake and backlog. Created against resolved, and whether the open count went up or down.
  4. Late, stuck, or at risk. From the overdue and untouched filters, each with an owner and a next step.
  5. Next month. Priorities, known absences, and dates that moved.
  6. Asks. Decisions or help needed, each with a name.

Aim for one screen. The filters and dashboard carry the detail. The report carries the judgement. If the same checklist of steps goes into every report, see where checklist steps should live.

Step 4: Make the report ticket appear every month #

The report gets written when it is a ticket with a due date in someone's queue. There are three ways to get that ticket.

Clone by hand Jira Automation rule Recurring Work Items for Jira
Who creates it A person, each month A Scheduled rule A schedule in the project
Month in the title Typed each time Smart values Date tokens such as {{now.monthName}}
Last weekday or a day that some months lack Remembered by a person Cron expression Built into the schedule
Uses Automation quota No Yes No
When it stops Someone forgets Disables after repeated failures Each run recorded with a reason

Cloning by hand is fine until the person who remembers goes on leave at month end, which is when it fails.

A Jira Automation rule with a Scheduled trigger and a Create work item action is the native option. Atlassian's trigger reference says you can "run the flow at a fixed rate (for example, every 7 days), or use a Cron expression for more complex schedules." A fixed rate drifts against the calendar, so a monthly report usually needs the cron form; our Jira cron expression guide has the monthly patterns. Each run counts toward your plan's automation usage, covered in Jira Automation pricing, and Atlassian notes 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 monthly report ticket is one of the simplest rules to write in it.

  1. Turn the app on for the project and choose who may schedule.
  2. Create a rule that repeats monthly, either on a day of the month (the 1st) or on a weekday position (the first Monday, or the last Friday).
  3. Name the ticket with tokens, for example Monthly report: {{now.monthName}} {{now.year}}. A misspelled token is refused when you save, so the typo never reaches a ticket title.
  4. Paste the outline from Step 3 into the description, with links to the four saved filters.
  5. Set the assignee, and the due date as an offset from the run, such as three days later.

If you pick a day like the 31st, the rule can move to the last day of shorter months instead of skipping them. It uses no Jira Automation quota, every run is recorded in the rule's history whether it created, skipped or failed, and it only creates tickets in the project it is set up in. It is free for up to 10 users.

One naming detail: the ticket created on 1 November reports on October. If you want the title to name the month being reported, create the ticket on the last working day of the month instead, or write the title as "Monthly report, written {{now.monthName}}".

When the manual way is enough #

You do not need a rule or an app if:

A scheduled ticket earns its place when the report goes to leadership or a client, when the writer rotates, or when a missed month is noticed by the reader before the team.

Frequently asked #

How do I filter Jira issues for last month? Use resolved >= startOfMonth(-1) AND resolved < startOfMonth(), swapping resolved for created or updated as needed. The bounds keep it to the previous calendar month.

Can Jira email a monthly report automatically? Yes. Save the filter and add a subscription with a monthly frequency. Atlassian states that only the first 200 results are sent.

Can Jira create a monthly report ticket on the first of every month? Yes, with a Jira Automation rule on a Scheduled trigger using a cron expression, or with a scheduling app such as Recurring Work Items for Jira, which creates it on the day you choose with the month in its title.

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