Blog ·

Jira patch management: run the monthly patch cycle as tickets

Jira patch management works best when every patch cycle is one ticket that appears on its own, on the right day, with the environments as subtasks and the exceptions recorded where an auditor can find them. Jira is not a patching tool. It will not scan your servers or push updates. What it does well is the part around the patching: who does it, by when, in which order, what was skipped and why, and proof that it happened every month. This guide sets that up from scratch and ends with the schedule that keeps it running.

Statements about Jira's built-in features are as of October 2026, from Atlassian's own documentation.

What Jira does in patch management, and what it does not #

Patching has two halves. The technical half belongs to your patching tool: the endpoint manager, the configuration management scripts, the cloud provider's update service. The process half is a list of decisions and checks that people make every cycle, and that half is where Jira helps.

Part of the cycle Done by Jira's role
Find missing patches Your scanner or endpoint manager Holds the link to its report
Decide what to apply The ops team A ticket with the decision written down
Test, then roll out by environment Your patching tool, run by people A subtask per environment, in order
Record what was skipped The ops team An exception ticket with an owner and an end date
Prove it happened Whoever an auditor asks A filter of resolved cycle tickets

If you only take one thing from this table: the cycle ticket is the record. Your patching tool knows what was installed. Only the ticket knows that someone decided to hold back a database patch until the vendor confirmed support, and who agreed.

Set up the patch cycle ticket #

Use one ticket per cycle, not one ticket per patch. A monthly cycle with forty patches across three environments is one piece of work with a few stages, and the board should show it that way.

A cycle ticket needs only a few fields:

The description is the runbook for this month. Keep the steps short and in order:

  1. Read this month's vendor releases and the scanner report.
  2. Note anything rated critical or already exploited, and decide whether it waits for the cycle or goes out now.
  3. Approve the patch list for the cycle.
  4. Roll out by environment, following the subtasks.
  5. Confirm the scanner report is clean, or that every remaining gap has an exception ticket.
  6. Resolve the cycle ticket with a one-line summary.

Subtasks per environment #

Patches go out in rings: test first, then staging, then production, then endpoints, with a pause between each to catch breakage. Make each ring a subtask of the cycle ticket.

Subtask Typical owner Done when
Test environment Ops engineer Patched, smoke tests pass
Staging Ops engineer Patched, application owners have checked their services
Production servers Ops lead or on-call Patched in the maintenance window, monitoring quiet
Endpoints Desktop support Deployment report shows the target coverage
Verify and close Cycle owner Scanner clean or exceptions filed

Subtasks keep the cycle ticket honest. A parent ticket with one subtask still open cannot quietly be marked done, and the board shows exactly which ring the cycle is stuck in. If you reuse the same subtasks every month, our Jira subtask template guide covers four ways to get them created automatically.

If production patching needs change approval in your company, the production subtask links to a standard change. Our Jira change management template covers how a pre-approved standard change differs from a normal one, which is usually what a monthly patch run should be.

Exceptions: the patches you did not apply #

Every patch cycle has a few patches that cannot go out. A vendor has not certified it, a legacy server cannot reboot this month, an application breaks on staging. These are the items auditors ask about, and the items most teams lose.

Give each one its own ticket with a type or label such as patch-exception, and make three fields mandatory:

An exception without a review date is a permanent hole with a ticket number. Put the review date in the Due date field, so the overdue filter below catches it. Link each exception to the cycle ticket it came from, so the October cycle shows its two exceptions next to it.

Critical patches that cannot wait #

The monthly cycle is for the routine. When a vendor releases a fix for a flaw that is already being exploited, you do not wait for the second Tuesday. Handle these as their own ticket, outside the cycle:

Keeping emergency patches out of the cycle ticket means the cycle's record still shows the routine, on time, every month. Mixing them makes it hard to tell later whether the routine was ever late.

Make the cycle ticket appear every month #

The process above only works if the ticket exists before anyone needs it. Here are the three ways to create it on schedule.

Clone by hand Jira Automation scheduled rule A scheduling app
Who creates the ticket A person, every month A rule A rule in the project
"Second Tuesday of the month" Whoever remembers Needs a cron expression Chosen in the form
Holiday in the patch week Whoever notices Up to the rule's logic Set once for the project
Subtasks created with it Cloned with the ticket Extra rule actions Part of the rule
Cost Time Counts toward your plan's automation usage App licence

Clone by hand #

Keep last month's cycle ticket as the model and clone it. This costs nothing and is fine while one dependable person owns patching. It fails in the month that person is on leave, which is also the month nobody notices it failed.

Jira Automation #

Jira Automation's Scheduled trigger can create the cycle ticket on a timer. 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 patch cycle tied to a vendor release day is the complex kind, so it needs cron, and our Jira cron expression guide covers the syntax and the schedules cron cannot express. Each run counts toward your plan's automation usage, explained in Jira Automation pricing. The same Atlassian page also says:

Scheduled flows that reach a Failure status for 10 consecutive executions will disable automatically.

On a monthly rule, ten failures is the better part of a year. Check the rule's audit log as part of each cycle.

A scheduling app #

Recurring Work Items for Jira is our app, and a monthly routine like a patch cycle is the job it was built for:

  1. Turn the app on for the ops project and choose who may schedule.
  2. Set the working week and add public holidays, then choose Move it to the next working day under If it falls on a non-working day, so a cycle that lands on a day off moves rather than appearing when nobody is in: a new rule runs on the day it falls on, holiday or not.
  3. Create a rule that runs on a weekday position, such as the second Tuesday of the month.
  4. Title it with tokens so each cycle is named for its month, for example Patch cycle {{now.monthName}} {{now.year}}.
  5. Add the environment subtasks, the patching label, the assignee and a due date as an offset from the run.

It uses no Jira Automation quota, because the scheduling is the app's own. Each created or failed run is written to the rule's history with its reason. A rule only creates tickets in the project it lives in. It is free for up to 10 users.

Reports an auditor will ask for #

Three saved filters answer most patch questions. Replace OPS with your project key.

  1. Did every monthly cycle happen this year? project = OPS AND labels = patching AND labels != emergency AND resolved >= startOfYear() ORDER BY resolved ASC
  2. Which exceptions are past their review date? project = OPS AND labels = patch-exception AND due < now() AND statusCategory != Done
  3. Is this month's cycle stuck? project = OPS AND labels = patching AND statusCategory != Done ORDER BY due ASC

Subscribe the team to the second filter weekly, so an expired exception lands in an inbox rather than waiting for the audit. The Jira weekly report guide shows how to turn filters like these into a short report.

When the manual way is enough #

If one person patches a small estate every month and never misses, a calendar reminder and a cloned ticket are enough. Add the exception tickets anyway, because they are the part you will be asked about. A schedule earns its place when patching is shared across people, when the cycle date follows a vendor's release day rather than a fixed date, or when you need a year of on-time cycles to show somebody.

For the rest of an ops team's routine, from backup checks to access reviews, see Jira for IT operations.

Frequently asked questions #

Can Jira do patch management? Jira tracks the process: the cycle, the rollout order, the exceptions and the record. The patches themselves are applied by your patching tool.

Should each patch be its own ticket? Usually not. One ticket per cycle, with subtasks per environment and separate tickets only for exceptions, keeps the board readable.

How do I create a ticket every Patch Tuesday? With Jira Automation, use a Scheduled rule with a cron expression for the second Tuesday. With Recurring Work Items for Jira, choose "second Tuesday" in the rule form and set the due date a few days after the run.