Monthly access review
Check who has access to what, every month, with one subtask per system.
1 work item, 6 subtasks · Monthly
See the template setEach 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.
$advisoryEpicThe line under each item is a suggested scope. Write your own in each work item's description.
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.
| Variable | What it fills in | Example |
|---|---|---|
$advisory | The advisory's name or CVE in the epic summary; a text variable you add | CVE-2026-1234 |
$parentSummary | The epic's name, inside each work item's description | Patch rollout, CVE-2026-1234 |
$advisory is a custom variable the app asks for when you apply the set. $parentSummary is built in.
Use one way, or more than one. Each way creates the same structure.
Apply it from the app when the work starts.
The app asks for any variables, so each run carries its own details.
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.
Call the app's API from a rule.
Use this when an event in Jira, such as a field change, should start the work.
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.
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.
Yes. Add a subtask per system under Patch the affected systems, or use a checklist if one person patches them all.
No. A person triages each advisory and applies the set if it matters. That keeps a human decision in the trail.
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.
Building Jira apps since 2017.