Blog ·
Jira for engineering managers: team view, reviews, rhythm
Jira for engineering managers comes down to three jobs: seeing how the team is doing without reading every ticket, running the reviews that keep the system healthy, and holding a management routine that nobody else will hold for you. Jira already has the data for the first job and the structure for the second. The third is where most managers fall back on memory and calendar invites, and it is where a handful of scheduled tickets help the most. This guide covers each job, the JQL worth saving, and a starter calendar of recurring engineering manager tickets.
Statements about Jira's built-in features are as of October 2026, from Atlassian's own documentation.
If you run the ceremonies for one team, Jira for scrum masters is the closer fit. If you own the backlog and the product decisions, read Jira for product managers. An engineering manager sits beside both and asks a different question of the same board: is this team set up to keep delivering, month after month?
What an engineering manager needs from Jira #
Your questions are about people, load and the health of the system. Each has a home in Jira.
| Question | Where the answer lives |
|---|---|
| Is anyone overloaded? | A filter of open work grouped by assignee |
| Is work stuck waiting for review? | A filter on the review status, sorted by last update |
| Are we drowning in unplanned work? | Created versus resolved, split by issue type |
| Is tech debt growing or shrinking? | A labelled debt backlog and its trend |
| Are bugs being handled in time? | Open bugs by priority and age |
| Did the operational chores happen? | Recurring tickets with an owner and a due date |
| Did my own follow-ups happen? | Your management tickets, labelled and filtered |
The last two rows are the ones that rarely live in Jira, and they are the ones a team notices when they slip: the access review nobody ran, the dependency upgrades that piled up for a year, the promised career conversation that never got booked.
Build a team view instead of reading every ticket #
A manager who reads every ticket becomes a bottleneck and stops seeing the pattern. Build one dashboard for the team and read it weekly. Replace TEAM with your project key.
| View | JQL |
|---|---|
| Open work per person | project = TEAM AND statusCategory = "In Progress" ORDER BY assignee |
| Waiting on review for two days | project = TEAM AND status = "In Review" AND updated <= -2d |
| Unplanned work this month | project = TEAM AND issuetype = Bug AND created >= startOfMonth() |
| Old high-priority bugs | project = TEAM AND issuetype = Bug AND priority in (Highest, High) AND statusCategory != Done AND created <= -14d |
| Unassigned and in a sprint | project = TEAM AND sprint in openSprints() AND assignee is EMPTY |
| Overdue team routine | project = TEAM AND labels = team-routine AND due < now() AND statusCategory != Done |
Status names vary between workflows, so check yours before saving the second filter. Put each filter on a dashboard as a filter results or pie chart gadget. Our Jira dashboard examples covers six layouts and the gadgets behind them.
Read the dashboard for trends, never as a scoreboard. Open work per person tells you where to ask a question. It says nothing about who works hardest, and using it that way teaches people to game the board.
Read load and flow, not just velocity #
Velocity is a planning tool for the team. For a manager, two other signals usually say more:
- Work in progress per person. Someone holding five tickets in progress is usually blocked on four of them. A short conversation beats a status meeting.
- Time waiting. Work that sits in review or in a "waiting for" state is the cheapest delay to remove. The second filter above finds it.
- The share of unplanned work. If bugs and interruptions take half the sprint, the plan was never the plan. Our Jira capacity planning guide covers reserving room for it.
The cumulative flow diagram on a board shows the same story over time: a band that keeps widening is a queue nobody is draining.
The reviews that keep the system healthy #
Engineering management is full of reviews that matter a great deal and are urgent on no particular day. That combination is exactly what gets skipped.
| Review | Typical cadence | What goes wrong without it |
|---|---|---|
| Tech debt review | Monthly | Debt only gets discussed during an outage |
| Dependency and library upgrades | Monthly | A framework falls three major versions behind |
| Bug backlog triage | Every two weeks | Old bugs are neither fixed nor closed |
| On-call and incident review | After each rotation | The same alert pages someone every week |
| Access review for repos and tools | Quarterly | People who left still have access |
| Hiring pipeline check | Weekly while hiring | Candidates wait days for feedback |
| Team health check | Monthly or quarterly | Problems surface as resignations |
| Roadmap and capacity check with product | Quarterly | The plan assumes a team you do not have |
Several of these have their own guides: Jira tech debt, Jira on-call rotation, Jira vulnerability management and Jira quarterly planning.
Every row is a recurring ticket. A ticket gives the review an owner, a due date and a place on the board the team already reads, and after a year it is a record of which reviews happened and what each one found.
Your own management routine #
Some of the routine is yours alone. It belongs in a small personal project or a label only you filter on, so it does not clutter the team board.
- One-on-one prep, before each recurring one-on-one: open the person's recent work, note last time's follow-ups.
- Feedback and recognition, weekly: one specific note to someone on the team.
- Career conversations, each quarter per person, so growth is not only discussed at review time.
- Performance review prep, before each review cycle, with the year's notes gathered in one place.
- Budget and tooling check, quarterly: seats, licences and subscriptions the team no longer uses.
Our Jira for personal task management guide shows how to keep a private list like this in Jira without anyone else seeing it.
How to create recurring engineering tickets in Jira #
There are three ways to get these tickets created on schedule.
| Clone by hand | Jira Automation scheduled rule | A scheduling app | |
|---|---|---|---|
| Who creates the ticket | You, each time | A rule | A schedule in the project |
| Setup | None | A rule per routine | A rule per routine, in a form |
| "First Monday of the quarter" | Whoever remembers | 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 template ticket per review and clone it when it is due. Our Jira task template guide covers the setup. It works while you remember, and it fails exactly when you are busiest.
A Jira Automation scheduled rule #
Jira Automation's Scheduled trigger can create a work item on a timer. Weekly and fortnightly routines fit a fixed rate. Monthly and quarterly ones need a cron expression, which our Jira cron expression guide explains, and every run counts toward your plan's automation usage, covered in Jira Automation pricing. Automation rules are also usually owned by a Jira admin, so a manager without admin rights may need to ask for each one.
A scheduling app #
Recurring Work Items for Jira is our app, and recurring tickets are its only job. Each routine becomes a rule in the team's project:
- Turn the app on for the project and choose who may schedule.
- Set the working week and add public holidays. A rule can 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
Tech debt review {{now.date}}, so this month's ticket is never confused with last month'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 team's schedules never create tickets in another team's project. It is free for up to 10 users.
A starter set of recurring engineering manager rules #
For a team of six to ten engineers:
- Bug triage, every second Tuesday. Description: run the old high-priority bugs filter, close what will never be fixed, assign what will.
- Tech debt review, on the first Wednesday of the month. Description: review the debt backlog, pick one item for the next sprint.
- Dependency upgrades, on the 15th of each month. Description: check for outdated libraries and runtime versions, file one ticket per upgrade.
- On-call review, every second Friday, after the rotation hands over. Description: list the pages, pick the noisiest alert to fix.
- Access review, on the first Monday of each quarter. Description: list repo and tool members, remove anyone who has left or changed teams.
- Team health check, on the last Thursday of the month.
Label every one team-routine, and the overdue filter above becomes your weekly check that the routine is alive. If you want a ready list of operational chores, Jira maintenance schedule and Jira hygiene have more.
When the manual way is enough #
If you manage one small team, the reviews happen in a fixed meeting with a standing agenda, and you reliably keep your own notes, you may not need any of this. A recurring calendar invite and a shared document can carry it. Scheduled tickets earn their place when you manage more than one team, when the routine must keep running while you are away, when an auditor or a senior leader asks for evidence that reviews happened, or when the chores need an owner other than you. For a broader comparison of the options, see Jira recurring tasks.
Frequently asked questions #
Should an engineering manager use the same Jira project as the team? For team reviews, yes, so the work is visible where the team already looks. Keep personal management notes, like one-on-one prep, in a private project or behind a label only you filter on.
Which Jira view shows whether a team is overloaded? A filter of in-progress work grouped by assignee, read alongside the cumulative flow diagram. Treat both as a prompt for a conversation, never as a performance measure.
How do I schedule a quarterly access review in Jira? Create a Jira Automation rule with the Scheduled trigger and a cron expression for the first Monday of the quarter, or create a rule in Recurring Work Items for Jira that repeats every three months on the first Monday.
How do I keep tech debt from being forgotten? Label debt tickets consistently, and put a monthly review ticket on the board that picks one item for the next sprint. Jira tech debt covers sizing and paying it down.