About this report

The Escalations report provides a list of escalations created for a specific PI. Escalations are work items that can be used to solicit a decision from the Program or Portfolio teams. Escalation examples include urgent customer support requests or Portfolio-level decisions needed on epic priorities. When escalations are created and tied to a sprint, all team members tied to the sprint receive a notification to work on a resolution.

This report reads as a data table/matrix. The report can be used to foster communication and transparency between Program-level and Portfolio-level stakeholders, to make sure guidance is provided and the escalations are ultimately resolved. This report is generated by selecting a specific PI. 


  1. Select the Reports icon from the left Navigation menu.
  2. Start typing the report's name in the Search box. 
  3. Once found, select the report.

Note: You can also use the categories on the left to search for the needed reports.


  1. PI must exist in the system and be tied to a program. 
  2. Sprints must be created and tied to a PI. 
  3. Escalations must be created and tied to a program, PI, and sprint. 

How are report values calculated? 

  • Escalation column = the name of the escalation; escalations are entered on the Escalations Grid/New Escalation panel.
  • Description column = the description of the escalation, as entered on the Escalations Grid/New Escalation panel.
  • Escalated by column = the user that created the escalation, as entered on the Escalations Grid/New Escalation panel.
  • Escalated on column = the date the escalation was created on the Escalations Grid/New Escalation panel.
  • Program column = the program the escalation is tied to, as entered on the Escalations Grid/New Escalation panel.
  • State column = a red X indicates the escalation is open and action is required; a green check mark indicates the escalation has been resolved. The escalation state is set via the Escalations Grid.


How to interpret this report

Escalations require collaboration between Program or Portfolio teams. A large volume of open escalations means action is required promptly, or a sprint/PI may be in jeopardy. Keep in mind a resolution to an escalation could be as simple as providing guidance via the Escalation Resolution panel (available by clicking the Take Action link in the Escalation Grid), or actually canceling a sprint, which is also an available option.   

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.