Blog ·
Jira for product managers: backlog, discovery and reviews
Jira for product managers comes down to three jobs: deciding what to build, keeping the backlog honest so engineering always knows what is next, and running the rhythm of reviews that tells you whether the last thing you shipped worked. Jira is strong at the second job and good at the third once you give it a schedule. The first job, discovery, can live in Jira too, but most product managers do better keeping raw ideas out of the delivery backlog. This guide walks through each job, the views worth opening every morning, and how to make the recurring product work appear on the board by itself.
Statements about Jira's built-in features are as of October 2026, from Atlassian's own documentation.
If you manage delivery dates and people rather than the product, our Jira for project managers guide is the closer fit. The two roles share a board and need different things from it.
What a product manager needs from Jira #
A project manager asks "will it ship on time?". A product manager asks "is this the right thing, and did it work?". That difference decides how you set Jira up.
| Question | Where the answer lives in Jira |
|---|---|
| What problems are we considering? | An ideas list, kept apart from the delivery backlog |
| What is next for engineering? | The top of the backlog, refined and ordered |
| How big is each initiative? | Epics, with their child work items |
| What did we ship this month? | A filter on resolved work, grouped by epic |
| Did it work? | A follow-up ticket per release, due after the data comes in |
| What is our routine? | Recurring tickets for reviews, feedback triage and reporting |
The mistake most product managers make is using the backlog as an ideas list. Every half-formed request goes in, nothing comes out, and after a year the backlog holds eight hundred items nobody will ever read. Engineering stops trusting it, and planning turns into a conversation about which items are still real.
Keep discovery out of the delivery backlog #
Raw ideas need somewhere to go so that the person who raised them feels heard. That place should not be the list engineering pulls from.
You have two practical choices:
- A separate ideas project. A small Jira project with a simple workflow: New, Under review, Accepted, Parked, Declined. Anyone can file into it. You review it on a schedule and move accepted ideas into the delivery project as epics or stories.
- A dedicated product discovery tool. Atlassian sells Jira Product Discovery for this job, and dedicated roadmapping tools exist outside the Atlassian family too. These add prioritisation fields, views by impact and effort, and links from an idea to the delivery work. They suit teams with a steady flow of customer input and a product manager whose main job is deciding.
Either works if the review actually happens. An ideas project nobody triages is the overgrown backlog with a different name. That review is the first recurring ticket in this guide.
When you accept an idea, write it up before it reaches engineering: the problem, who has it, how you will know it is solved. Our Jira epic template has a structure you can copy into every new initiative.
Keep a backlog worth reading #
The delivery backlog is the product manager's main output in Jira. Engineering reads it every sprint, so it is worth an hour a week.
A backlog in good shape has three zones:
- The top two sprints. Refined, estimated, with acceptance criteria. Anyone on the team could pick up the next item without asking you a question.
- The next quarter. Epics with a sentence of intent and a rough size. Not broken down yet, on purpose.
- Everything else. Ideally small. If it is not in the next quarter and nobody will miss it, close it with a resolution such as Won't do and a comment. Closing is a decision, and it is reversible.
Our groomed backlog guide shows what each zone looks like on a real board, and Jira for sprint planning covers the meeting that consumes it. For a board-wide check on stale and orphaned items, Jira hygiene has the filters.
Refinement is a habit, not an event. A backlog groomed once before a big planning session drifts back within a month. A weekly slot, with a ticket that reminds you, holds it in shape.
The views a product manager reads every day #
Save these as filters and pin them to a dashboard. Replace PROD with your project key.
| View | JQL |
|---|---|
| What is in progress now | project = PROD AND sprint in openSprints() AND statusCategory = "In Progress" |
| Blocked or waiting | project = PROD AND status in ("Blocked", "Waiting") AND updated <= -2d |
| Shipped in the last 30 days | project = PROD AND resolved >= -30d ORDER BY resolved DESC |
| Bugs reported this week | project = PROD AND type = Bug AND created >= startOfWeek() |
| Unrefined items near the top | project = PROD AND sprint is EMPTY AND "Story point estimate" is EMPTY AND statusCategory = "To Do" |
The last one matters most before planning. If it returns anything in the first twenty rows of the backlog, the next sprint will start with questions. Field names vary between team-managed and company-managed projects, so check the estimate field name on your own site.
The product manager's routine nobody puts on the board #
Delivery work gets tickets because somebody asks for it. The product manager's own routine does not, because nobody asks. It is the part that slips in a busy release week. A typical calendar:
| Routine | Cadence | What goes wrong without a ticket |
|---|---|---|
| Backlog refinement | Weekly | The top of the backlog goes stale and planning stalls |
| Ideas and feedback triage | Weekly | Requests pile up and the people who sent them hear nothing |
| Metrics review | Weekly or every two weeks | Nobody notices a feature that is not used |
| Release follow-up | Two to four weeks after each release | "Did it work?" is never answered |
| Roadmap update | Monthly | The roadmap stakeholders read is out of date |
| Customer interview round | Monthly | Discovery happens only when a deal forces it |
| Quarterly planning prep | Every quarter | Priorities are set the night before the meeting |
| Competitor and market scan | Every quarter | You learn about a rival's launch from a customer |
Every row is a recurring ticket. Making each one a ticket gives it an owner, a due date and a place on the same board as the work it shapes. The release follow-up is the row with the most value: a ticket that asks "did this change the number we wanted?" turns shipping into learning.
How to create recurring product tickets in Jira #
There are three ways to get these tickets onto the board, and the right one depends on how many routines you have and who maintains them.
| Clone by hand | Jira Automation scheduled rule | A scheduling app | |
|---|---|---|---|
| Who creates the ticket | You, every cycle | A rule | A schedule in the project |
| Setup | None | A rule per routine | A rule per routine, in a form |
| "First Monday of the month" | Whoever remembers | Needs a cron expression | Chosen in the form |
| You are on leave | The ticket is not created | Created on time | Created on time |
| Cost | Your time | Counts toward your plan's automation usage | App licence |
Clone by hand #
Keep a master ticket per routine and clone it each cycle. For one weekly refinement slot, that is fine. It fails in the weeks when you are busiest, which are the weeks the review mattered most.
A Jira Automation scheduled rule #
Jira Automation's Scheduled trigger can create a work item on a timer. A weekly triage ticket is simple. Monthly and quarterly routines need a cron expression; our Jira cron expression guide covers the syntax and what it cannot say. Each run counts toward your plan's automation usage, explained in Jira Automation pricing. If your team already runs a few Automation rules comfortably, this is a natural next step.
A scheduling app #
Recurring Work Items for Jira is our app, and recurring tickets are the whole job. A product routine becomes a rule in the project:
- Turn the app on for the product project and choose who may schedule.
- Set the working week and add public holidays. A rule can then roll forward or back to a working day, or skip the occurrence, when its date lands on a day off.
- Create a rule per routine. The schedule options are every N days, chosen weekdays every N weeks, a day of the month, or a weekday position such as the first Monday or the last Friday of the month.
- Name each ticket with tokens, for example
Metrics review {{now.date}}, so this week's ticket is not confused with last week's. - Put the checklist in the description and set the assignee, labels and a due date relative to the run.
It uses no Jira Automation quota, and every run, whether it created, skipped or failed, is written to the rule's history with its reason. A rule is scoped to the project it lives in, so the product team's schedules never create tickets in anyone else's project. It is free for up to 10 users.
A starter set of recurring product rules #
A set most product managers can adopt on day one:
- Backlog refinement, every Tuesday. Description: check the top twenty items have acceptance criteria and an estimate, split anything too large, close anything no longer wanted.
- Ideas triage, every Thursday. Description: move each new idea to Accepted, Parked or Declined, and reply to whoever raised it.
- Metrics review, every second Monday, with headings for What moved, What we expected, What to look into.
- Roadmap update, on the first Monday of the month, so stakeholders read a roadmap less than a month old.
- Customer interview round, on the second Wednesday of the month. Description: book three conversations, link the notes to the ideas they touch.
- Quarterly planning prep, every three months on the 1st, due two weeks before the planning session.
- Market scan, every quarter, with a short template for what changed and what it means for the roadmap.
The release follow-up does not fit a calendar, because releases do not. Create it when you ship, with a due date three weeks out, and link it to the release epic. A Jira task template keeps its questions the same every time.
Add a product-routine label to every recurring ticket. Then one filter, project = PROD AND labels = product-routine AND due < now() AND statusCategory != Done, shows which part of your own job has slipped.
When the manual way is enough #
If you own one small product, refine the backlog in the same weekly meeting every week, and never miss it, you do not need any of this. A recurring calendar event and a habit will do. Scheduled tickets earn their place when the routine has more than three or four parts, when it needs to survive your holiday, or when you want a record of which reviews actually happened.
For a wider look at the options for repeating work, see Jira recurring tasks and Jira reminder.
Frequently asked questions #
Should product managers and engineering share one Jira project? Usually yes for delivery work, so the backlog and the sprint live in one place. Keep raw ideas in a separate project or a discovery tool so the backlog stays readable.
Should a product manager write every story? No. Write the epic and the problem it solves; let the team break it into stories during refinement. Stories written alone tend to miss how the work will actually be done.
How do I get a metrics review ticket every two weeks? Clone one by hand, create a Jira Automation rule with the Scheduled trigger, or create a rule in Recurring Work Items for Jira that repeats every two weeks on Monday with the headings in the description.
How do I stop the backlog growing forever? Close items that are not in the next quarter and that nobody will miss, with a clear resolution and a comment. Put a weekly refinement ticket on the board so the pruning happens on a schedule.