SupportBook a demoTry it free

Patch rollout template set for Jira

Roll out every vendor patch the same way, from listing the affected systems to closing the advisory, with an epic named for the advisory.

1 epic · 4 work items · On request

Read: From advisory to patched: vulnerability management in Jira · The vulnerability management use case

Illustration of the Patch rollout template set in the app, with sample data.

The structure

What it creates

Each run creates an epic named for the advisory and four work items under it. Link the epic to the advisory work item, and you have a trail from "the vendor told us" to "we fixed it".

The set is the third step of our vulnerability management use case: a feed creates the advisory work item, a reviewer triages it, and the reviewer applies this set when a system is affected.

  • Patch rollout, $advisoryEpic
    • List the affected systemsEvery system running the affected version, with its owner.Task
    • Patch the affected systemsApply the patch, in a maintenance window if needed.Task
    • Verify the patchCheck each system runs the fixed version.Task
    • Close the advisoryRecord the outcome on the advisory work item and close it.Task

The line under each item is a suggested scope. Write your own in each work item's description.

What fills in

Variables

Variables fill in what changes from run to run. They work in text fields, such as the summary and description. A user variable fills in a person field, such as Assignee.

Variables in the Patch rollout template set
VariableWhat it fills inExample
$advisoryThe advisory's name or CVE in the epic summary; a text variable you addCVE-2026-1234
$parentSummaryThe epic's name, inside each work item's descriptionPatch rollout, CVE-2026-1234

$advisory is a custom variable the app asks for when you apply the set. $parentSummary is built in.

When it runs

How to run it

Use one way, or more than one. Each way creates the same structure.

  1. 01

    On request

    Apply it from the app when the work starts.

    The app asks for any variables, so each run carries its own details.

  2. 02

    From a workflow transition

    Add the app's post function to the transition that marks an advisory as Affected.

    This works in company-managed spaces. The set is applied the moment the work item moves.

  3. 03

    From Jira Automation

    Call the app's API from a rule.

    Use this when an event in Jira, such as a field change, should start the work.

Who it's for

IT and security teams that patch the products they run, and need to show how each advisory was handled.

It pairs with the vendor security advisories feed collection and the Triage result comment template.

When not to use it

If a vulnerability management platform already tracks remediation, link its tickets instead of copying them into Jira.

For fleet-wide updates your endpoint tool rolls out on its own, record the rollout, not each device.

Patch rollout: common questions

Can we track each affected system?

Yes. Add a subtask per system under Patch the affected systems, or use a checklist if one person patches them all.

Does it start from the feed by itself?

No. A person triages each advisory and applies the set if it matters. That keeps a human decision in the trail.

Can we set a due date by severity?

Set due dates on the work items after you apply the set. Variables fill in text fields, not dates.

Other template sets that teams use alongside this one.

Browse the template library
Access review, $todayMonthly
Review Jira access
Review email and calendar access
Review code repository access
+3 more
ExampleOperations

Check who has access to what, every month, with one subtask per system.

1 work item, 6 subtasks · Monthly

See the template set
Bug: $bugTitle
Reproduce the bug
Triage and assign
Verify the fix
ExampleEngineering

Report, triage and verify every bug with the same steps.

1 bug, 3 subtasks · On request

See the template set
Release $version
Freeze the release branch
Run the release tests
Update the version in the docs
+6 more
GuideEngineering

Your release steps as a checklist, ready for each version.

1 work item, 9 checklist items · On request

See the template set
Part of AppsDelivered

Repeatable work, delivered.

Building Jira apps since 2017.

AppsDelivered CommentsReuse your team's replies.See AppsDelivered CommentsAppsDelivered FeedsTurn new posts into work items.See AppsDelivered Feeds