Blog ·

Jira for manufacturing: plant requests and the maintenance calendar

Jira for manufacturing works best for the work around the line rather than the line itself. Engineering changes, tooling requests, quality investigations, preventive maintenance, calibration and audit preparation all move between people and carry a due date, which is what Jira tracks well. It does not replace an MES, an ERP or a dedicated maintenance system for work orders tied to meters and spare parts. This guide sets Jira up for the work it suits, then makes the recurring maintenance, calibration and quality calendar arrive as tickets by itself, so a check never depends on one person's memory.

If you are still deciding whether Jira belongs in your plant at all, there is a section near the end on when another tool is the better call.

Where Jira fits in a manufacturing business #

A plant usually already runs an ERP for orders and inventory, often an MES on the shop floor, and sometimes a maintenance system. Jira earns its place in the gaps between them: requests that pass from production to engineering to quality, and the routine checks that belong to a team rather than to a machine's controller.

Job Where it lives in Jira What repeats
Engineering changes One work item per change request, with an approval status Weekly change review board
Quality issues One item per nonconformance or corrective action Monthly corrective action review
Tooling and fixtures An item per tool request or repair Tool condition checks per shift pattern
Preventive maintenance A maintenance project, one component per line or machine Weekly, monthly and quarterly service tasks
Calibration Items per instrument group Calibration due dates, usually yearly
Audits and compliance An operations project Internal audits, management review, certificate renewals

Two or three projects cover most small and mid-sized plants. One for engineering and quality, one for maintenance and calibration, one for running the site. More than that produces boards nobody opens.

Set it up in six steps #

  1. Create a team-managed project for engineering and quality, using the Kanban template. Give each product line or customer an epic, and each change request or nonconformance its own work item under it.
  2. Create a maintenance and calibration project. Every line, machine or instrument group gets a component or a label, so a filter can show one machine's history.
  3. Create an operations project for health and safety, audits, IT, and HR requests. Split the areas with labels rather than more projects.
  4. Keep workflows short. To do, In progress, Waiting on parts, Done. An engineering change may need an Approval status, but resist one status per department.
  5. Turn on due dates and assignees. Every filter below relies on them, and on a plant floor a task with a date and no owner is the one that slips.
  6. Decide who needs access. Operators and technicians often need only the maintenance project. Suppliers and customers usually should not see your corrective action log.

Leave custom fields, complex permission schemes and automation until a real problem asks for them.

Filters the plant manager actually opens #

A board shows everything. A plant or maintenance manager needs to know what is due this week, what has slipped and what is stuck waiting on parts. Three saved filters cover most of it:

Filter JQL Who opens it
Due this week due <= 7d AND statusCategory != Done ORDER BY due Maintenance lead, every Monday
Overdue due < 0d AND statusCategory != Done Plant manager, daily
Waiting on parts status = "Waiting on parts" ORDER BY updated Whoever chases purchasing

Subscribe the plant manager to "Overdue" every morning. A filter subscription is a free early warning, and it surfaces the overdue calibration that nobody wants to mention before an audit. The Jira dashboard examples show how to put the same filters on one page for the weekly production meeting.

The preventive maintenance and calibration calendar #

This is where plants struggle most. Breakdowns are visible because the line stops. The checks that prevent them come round every week, month or year and belong to whoever did them last. Typical recurring work:

An overdue calibration is more than paperwork. It can put every part measured since the last good check in question. When these tasks live in a spreadsheet or a supervisor's notebook, they lapse the week that person is on leave or changes shift. As tickets with due dates and owners, they appear in the filters above like any other work. The question is how they get there each cycle.

Approach Effort each cycle What goes wrong
Clone last cycle's ticket by hand Someone clones and redates it The person who remembers is the system
Create a year of tickets up front One long day each January Machines are added and retired, the list goes stale
A Jira Automation scheduled rule None, once the rule exists Each run spends the automation allowance
A recurring-issue app None, once the schedule exists One more app on the site

Cloning by hand #

For two or three checks, cloning works. When the ticket closes, clone it and set the next due date. It fails quietly, because nobody notices a ticket that was never created.

Jira Automation #

Jira Automation's Scheduled trigger is Jira's own clock. Atlassian's trigger documentation, as of October 2026, describes it this way:

"You can run the flow at a fixed rate (for example, every 7 days), or use a Cron expression for more complex schedules."

That suits a handful of simple schedules such as "every Monday". Calendar rules such as "the first working day of each month" need cron, which the Jira cron expression guide walks through. The same page notes that "Scheduled flows that reach a Failure status for 10 consecutive executions will disable automatically", so a weekly lubrication rule that keeps failing goes quiet after ten weeks. Every run also spends from the site's monthly automation allowance, and the Jira Automation pricing guide explains how that is counted.

A recurring-issue app #

This is the approach we build for. Recurring Work Items for Jira lets you write each schedule once, in one project, and from then on the ticket appears by itself. For a maintenance and calibration project that means:

It runs its own scheduler, so it does not spend your Jira Automation allowance, and it is scoped to the projects you turn it on in, so the maintenance calendar does not spill into the engineering board. It is free for up to 10 users. See how a rule is set up.

A starter calendar for a small plant #

A concrete set of schedules to copy into the maintenance and operations projects. Adjust the intervals to your manufacturers' manuals, your own machines and your local regulations, which this table does not replace.

Ticket Schedule Owner Subtasks
Lubrication round Every Monday, per line Maintenance technician Points per machine, top up, log anomalies
Safety walk Every Friday Shift supervisor Guards, walkways, spills, sign off
Forklift inspection First working day of the month Warehouse lead Checklist per truck, raise defects
Corrective action review Monthly Quality manager Open actions, overdue actions, effectiveness checks
Bearing and belt inspection Quarterly, per machine Maintenance lead Inspect, measure, order parts
Instrument calibration Once a year, per instrument group Quality technician Book the lab, update the register, file certificates
Internal audit Once a year, per process Quality manager Plan, audit, report, raise actions

Give every recurring ticket a named owner, not a team. A ticket assigned to "Maintenance" is assigned to nobody. For the broader picture of planned work, see the Jira maintenance schedule guide; for the buildings and utilities side, Jira facilities management; and for keeping track of the machines and instruments themselves, asset management for Jira. If the checklists are long, the Jira checklist template guide covers where the steps should live.

When Jira is the wrong tool #

Jira suits the office and engineering side of a plant and fits some floor work poorly. Look elsewhere, or alongside it, when:

If those describe most of your work, keep Jira for engineering requests, quality actions and the calendar of routine checks, and let the specialist systems run the rest.

Summary #

For a manufacturing business, Jira works best kept small: one project for engineering and quality, one for maintenance and calibration, one for running the site, three filters and one owner per ticket. The recurring maintenance, calibration and audit tasks are what keep lines running and audits clean, so make those tickets arrive on their own, by an Automation rule for a few simple schedules, or with a recurring-issue app when the calendar grows. For a fuller comparison of the options, read our guide to Jira recurring tasks.