Patch rollout
An epic and four work items, from listing the affected systems to closing the advisory.
1 epic, 4 work items · On request
See it in the template libraryEach step is one person's action with one app. Your team moves the advisory from step to step in Jira, the same way it moves any other work.
Subscribe to your vendors' advisory feeds with a reviewer. Each new post becomes a work item assigned to that person.
You set up the subscriptions once. After that, the reviewer finds each new advisory in Jira, next to the rest of the team's work.
Start from the Vendor security advisories collectionIllustration of the app in Jira Cloud, with sample data.
The reviewer adds the Triage result comment template, and the team answers in an internal thread.
The template asks for the same three things every time: the result, the systems and when to patch. The people who run those systems reply in the thread, so the decision and the reasons behind it stay on the advisory.
Illustration of the app in Jira Cloud, with sample data.
Apply the Patch rollout template set from the app and type the advisory name. It creates the epic and its work items. Link the epic to the advisory.
Every rollout gets the same four steps, from listing the affected systems to closing the advisory. If the triage result is Not affected, the reviewer closes the advisory work item and stops there.
See the Patch rollout set in the template libraryIllustration of the app in Jira Cloud, with sample data.
One advisory, one decision and one rollout, linked together in Jira.
When someone asks later what happened with an advisory, open its work item. The triage result, the thread and the linked rollout epic show what was decided, who decided it and what was done.
Each app installs on its own from the Atlassian Marketplace. Use all three, or start with the step your team needs most.
Step 01: turns each new advisory into a work item with a reviewer.
Free on the Atlassian Marketplace.
Step 02: holds the Triage result template and the internal thread.
Free for up to 10 users. Larger teams get a 30-day free trial, then pay per user, billed by Atlassian.
Step 03: holds the Patch rollout template set.
Free for up to 10 users. Larger teams get a 30-day free trial, then pay per user, billed by Atlassian.
The template set, comment template and feed collection behind the three steps.
An epic and four work items, from listing the affected systems to closing the advisory.
1 epic, 4 work items · On request
See it in the template libraryThree lines the reviewer fills in: the result, the systems and the patch date. Save it once in the comments app, and every advisory gets its answer in the same shape.
See AppsDelivered CommentsAdvisory feeds from the vendors in your stack, checked every hour, with each feed's link ready to copy into the feeds app.
See the feed collectionNo. Each app does its own step, and your team moves the work along in Jira.
Yes. In a company-managed space, a workflow transition can apply a whole template set, so moving the advisory to Affected builds the Patch rollout structure.
No. Each step works without the others. You can start with the Patch rollout set and log advisories by hand, then add the feeds app later.
Book a demo with your own vendors and systems in mind, or try each app in your Jira site.