Vulnerability management sounds like a tool you buy. For most teams it starts as a process: hear about the advisory, decide if it matters, patch what’s affected, and prove you did. Jira can hold all four steps. Here is how we set it up with our three apps, one step and one person at a time.
Step 1: The advisory arrives as a work item
Subscribe to your vendors’ official advisory feeds in AppsDelivered Feeds. Each new advisory becomes a work item in your Security space, assigned to the reviewer for that feed. Nobody has to watch a mailbox.
Step 2: The reviewer triages it
The reviewer reads the advisory and records a decision. A comment template keeps every decision in the same shape: affected or not, which systems, and when the patch should land. Questions for other teams go in a thread under the decision, so the answer stays with it.
Step 3: If affected, roll out the patch
The reviewer applies a Patch rollout template set. It creates an epic with the same work items every time: list the affected systems, patch them, verify the patch, close the advisory. A custom variable puts the advisory’s name in the epic. The reviewer links the epic to the advisory work item.
What you can show afterwards
- Every advisory received, from the feed work items
- Every decision, from the triage comments
- Every patch, with its verification step, from the rollout epics
That is a complete trail from “the vendor told us” to “we fixed it”, without a separate tool. Our vulnerability management use case shows the full flow with each app’s part.



