How can you create a complete structure for an Incident Review in just a few clicks?

[#1]

Incidents happen…
We usually do everything we can to prevent them, but we also understand that, despite our best efforts, they can still occur.

Beyond simply acknowledging that an incident might happen, it's important to have a solid plan in place for what to do when it does.

Effective incident management isn’t just about:

• Create the issue

• Identifying the root cause

• Fixing the problem

It also includes a set of supporting activities carried out in parallel and after completion, for example:

• Establishing internal and external communication

• Conducting analysis

• Implementing resolution and risk mitigation

• Documenting the incident summary 

All of this is to smoothly handle the issue, understand it, and prevent it from occurring in the future.

To structure these activities and manage the incident effectively, a good practice is to create a hierarchy in Jira that includes parent and child work items:

Such a structure is often nested and forms a tree of relationships.
For example, work item INC-109 (and others) linked to my Epic also has its Subtasks:

Two key characteristics of this type of structure are:

• Multi-level nesting – allowing you to break down the process into clear, manageable steps 🔗

• Repeatability – since the process remains the same for each incident, the structure can be reused every time 🔄

What are the disadvantages?

• Time-consuming recreation of structures each time the incident occurs 😪
• Risk of skipping a task or making a human error⚠️

Suggested way to speed up this process using the Issue Templates app:

1. Create the structure once

2. Mark it as a template

3. Add Dynamic Variables and Smart Defaults to indicate the values that may vary with each occurrence of the incident, e.g., Incident ID, Prepare, Incident Date, 

From now on, whenever an incident occurs, you can use the template to generate the full structure in just a few clicks: