Post-Creation Priority Changes(5.5.7)

Priority changes after issue creation are a normal part of agile work — requirements evolve and priorities shift. But a steady pattern of de-escalations (lowering priority after creation) means priorities set at creation are being lowered later, and the question is whether that is triage correcting an initial guess or a target being moved after it was missed.

What you can conclude

• A consistent pattern of more de-escalations than escalations suggests that priorities are being set too high at creation and corrected later — initial triage may need improvement.
• Escalations that frequently result in reopened issues suggest that urgency-driven priority changes are being applied without the capacity to deliver at the higher priority level.
• A balanced, low-volume distribution of post-creation priority changes indicates stable, accurate initial prioritization.

How this chart works

Weekly dual-series bar chart showing escalated (priority raised) versus de-escalated (priority lowered) issues side by side. Use the date and project filters to focus on specific teams or periods.

The week in progress is shown at its count so far. Because the week is not yet complete, it covers only what has been recorded up to now and can only grow as the week closes.