Blog ·
Jira facilities management: requests and planned maintenance
Jira facilities management works when you split the job in two. Reactive work, such as a broken light, a jammed door or a leaking tap, comes in as requests and goes through a queue. Planned work, such as filter changes, fire alarm tests, lift servicing and contractor visits, comes round on a calendar and should arrive as tickets on the day it is due. Jira handles the first half out of the box. The second half is where most facilities teams lose track, because the calendar ends up in a spreadsheet or in one person's diary. This guide sets up both halves, then shows how to make the planned maintenance tickets create themselves.
Statements about Jira's built-in features are as of October 2026, from Atlassian's own documentation.
What facilities work looks like in Jira #
A facilities team usually looks after several kinds of work at once, and each kind wants a slightly different home.
| Kind of work | Example | Where it lives in Jira | How it arrives |
|---|---|---|---|
| Reactive requests | "Meeting room 3 projector is dead" | A service project queue, or a team project with a request type | Staff raise it |
| Planned maintenance | Monthly emergency lighting test | The facilities project, one work item per visit | On a schedule |
| Statutory inspections | Annual gas safety check, fire risk assessment review | The facilities project, labelled statutory |
On a schedule, with a hard due date |
| Contracts and renewals | Cleaning contract, waste collection, insurance | The facilities project, labelled contract |
On a schedule, ahead of the end date |
| Moves and projects | Office move, refit, new desk layout | An epic per project | Planned by hand |
The reactive half is visible because people complain when it is late. Nobody complains about a fire door inspection that did not happen until an auditor or an inspector asks for the record. That is why the planned half needs more structure, not less.
Set it up in five steps #
- Pick the project type for requests. If you already have Jira Service Management, a service project gives staff a portal to raise requests and gives you queues and request types. If you only have Jira, a team-managed project with a "Facilities request" work type and a simple form works for a small office.
- Create one facilities project for planned work, using the Kanban template. Keep it separate from the request queue so the calendar is not buried under a hundred lightbulb tickets.
- Use components or labels for sites and areas.
site-london,site-leeds,hvac,fire,water,lifts,cleaning. Filters and dashboards all build on these, so decide the list once and stick to it. - Keep the workflow short. To do, Scheduled, In progress, Waiting on contractor, Done. "Waiting on contractor" matters in facilities more than anywhere else, because so much of the work is done by someone outside the team.
- Make due date and assignee required on planned work. Every report below depends on them. A statutory check with no date is a check that never shows up as overdue.
Leave custom fields until a real question needs one. A "Contractor" field is often the first one worth adding, once you want to filter by who does the work.
The asset and equipment register #
Planned maintenance is always maintenance of something: a boiler, a lift, a fire alarm panel, a fleet of air conditioning units. You need a list of those things somewhere Jira can point to.
You have three realistic choices:
- A spreadsheet linked from the project. Fine for a single building with a few dozen assets. Each maintenance ticket names the asset in its summary.
- One work item per asset, in its own work type, with the maintenance tickets linked to it. This keeps the history of every visit one click away from the asset, at the cost of a few more items on the board.
- A dedicated asset tool. Jira Service Management includes an assets feature on some plans, and there are Marketplace apps built for asset registers. Worth it once you have hundreds of assets across several sites.
Our guide to asset management for Jira compares these in more detail. For this article, what matters is that each asset has a name you will use the same way in every ticket: Boiler B1, Leeds, not "the boiler".
The planned maintenance calendar #
This is the heart of facilities management, and the part that most often lives outside Jira. A typical planned preventive maintenance (PPM) calendar for an office building looks like this:
| Frequency | Typical jobs |
|---|---|
| Weekly | Fire alarm call point test, emergency exit walk, water outlet flushing for little used taps |
| Monthly | Emergency lighting flick test, fire extinguisher visual check, first aid kit check, water temperature checks |
| Quarterly | Air conditioning filter change, gutter and drain check, pest control visit |
| Every six months | Lift service, fire alarm system service by contractor |
| Yearly | Emergency lighting full duration test, gas safety check, electrical portable appliance testing, fire risk assessment review, insurance renewal |
Your list will differ. Building type, local regulations and the manufacturer's service intervals all decide what goes on it, and this table does not replace any of them. Check with whoever is responsible for compliance in your building before you treat it as complete.
What all of these jobs share is that nobody forgets them in the first month. They get forgotten in the eighth month, when the person who set up the spreadsheet is on leave, or has left. Moving the calendar into Jira as tickets with owners and due dates means a missed job shows up in the same overdue filter as everything else.
Getting the planned tickets created on time #
There are four ways to get those tickets into the facilities project each cycle. They suit different sizes of calendar.
| Approach | Effort each cycle | What goes wrong |
|---|---|---|
| Clone last time's ticket by hand | Someone clones and redates it | The person who remembers is the system |
| Create a year of tickets every January | One long afternoon | Assets change, the list goes stale by spring |
| Jira Automation scheduled rules | None, once each rule exists | Calendar rules need cron, and each run spends automation usage |
| A recurring-issue app | None, once each schedule exists | One more app on the site |
Cloning by hand #
For three or four jobs this is fine. When the ticket closes, clone it and move the due date on. It fails quietly, because a ticket that was never created does not appear in any overdue filter. The bulk clone guide covers the mechanics if you go this way.
Jira Automation #
As of October 2026, Jira Automation's Scheduled trigger can create a work item on a fixed interval or on a cron expression. "Every Monday" is easy. "The first working day of each month" or "the second Tuesday of every quarter" needs cron, which our Jira cron expression guide walks through, traps included. Every run counts toward the automation usage allowance on your plan, and the Jira Automation pricing guide explains how that is counted. A facilities calendar of forty jobs is forty rules, each one maintained separately.
A recurring-issue app #
This is the approach we build for. Recurring Work Items for Jira lets you write each schedule once, inside the facilities project, and from then on the ticket appears on its own. For a planned maintenance calendar that means:
- daily, weekly, monthly and quarterly rules with working-day and holiday handling, so a Monday test never lands on a bank holiday when the building is shut;
- dynamic titles, so the job arrives as "Emergency lighting test, October 2026" rather than a copy of last month's title, which makes a search for one month's records trivial (the token reference lists what you can put in a title);
- subtask checklists, so "Quarterly HVAC service" arrives with its steps already listed for whoever does each part;
- a run history for each rule that records what was created, skipped or failed, and why.
It runs its own scheduler, so it does not spend your Jira Automation usage. It is scoped to the projects you turn it on in, so the facilities calendar stays in the facilities project and does not spill onto the request queue or anyone else's board. It is free for up to 10 users. See how a rule is set up.
A starter calendar to copy #
A concrete set of schedules for a single office building, as rules in the facilities project. Adjust the days, the owners and the jobs to your own building.
| Ticket | Schedule | Owner | Subtasks |
|---|---|---|---|
| Fire alarm call point test | Every Monday | Facilities coordinator | Test the call point for this week, log the result |
| Emergency lighting flick test | First working day of the month | Facilities coordinator | Walk each floor, note failed fittings, raise repairs |
| Water temperature checks | First working day of the month | Facilities coordinator | Test outlets nearest and furthest from the tank, record readings |
| HVAC filter change | Quarterly | Contractor, tracked by facilities manager | Book the visit, confirm completion, file the sheet |
| Lift service | Every six months | Facilities manager | Book the engineer, file the report |
| Fire risk assessment review | Once a year | Facilities manager | Review, update actions, sign off |
| Cleaning contract renewal | Once a year, two months before the end date | Facilities manager | Review performance, get quotes, renew or retender |
Give every recurring ticket one named owner, not a team. A ticket assigned to "Facilities" is assigned to nobody. When the work is done by a contractor, the owner is the person who books and checks them, and the ticket moves to "Waiting on contractor" while they are on site.
The reports a facilities manager opens #
A board shows everything. A facilities manager wants to know what is due, what slipped and what is stuck with a contractor. Three saved filters cover most of it:
| Filter | JQL | Who opens it |
|---|---|---|
| Due this week | project = FAC AND due <= 7d AND statusCategory != Done ORDER BY due |
Facilities team, every Monday |
| Overdue statutory checks | project = FAC AND labels = statutory AND due < 0d AND statusCategory != Done |
Facilities manager, daily |
| Waiting on contractor | project = FAC AND status = "Waiting on contractor" ORDER BY updated |
Whoever chases suppliers |
Subscribe the facilities manager to "Overdue statutory checks" every morning. A filter subscription costs nothing and catches the inspection nobody wants to mention at the monthly review. The Jira dashboard examples show how to put the three filters on one page, and the Jira monthly report guide covers turning them into a report for the people who sign off the budget.
The completed tickets are your maintenance record. When an auditor asks for a year of emergency lighting tests, a filter on the label and the summary answers it, as long as every visit was a ticket that someone closed with the result attached.
When the manual way, or another tool, is enough #
Jira is a good fit for a facilities team that already uses it, or that sits close to an IT or operations team that does. It is not always the right answer:
- A single small office with a dozen jobs a year can run perfectly well on a shared calendar and a checklist. The overhead of a project is not worth it.
- Large estates with many sites, meters and engineers in vans are better served by a dedicated computer aided facilities management (CAFM) or maintenance management system, with mobile job sheets and parts stock built in.
- If nobody will own the board, Jira becomes a list of stale tickets within a quarter. A planned calendar only works when someone closes the tickets.
If your team is somewhere in the middle, Jira handles both halves well: requests through a queue, planned maintenance through tickets that arrive on their own. For the general version of the scheduled half, read our Jira maintenance schedule guide, and for a comparison of every way to repeat work in Jira, the guide to Jira recurring tasks.
Summary #
Facilities management in Jira comes down to two halves. Reactive requests go through a queue, which Jira or Jira Service Management handles out of the box. Planned maintenance and statutory checks go into a facilities project as tickets with one owner and a due date each, built from an asset list everyone names the same way. The planned half is the one that slips, so make those tickets create themselves: Automation rules for a handful of simple schedules, or a recurring-issue app once the calendar grows past what you want to maintain rule by rule.