Post-Creation Priority Changes

Priority changes after issue creation are a normal part of agile work — requirements evolve and priorities shift. But a systematic pattern of de-escalations (lowering priority after creation) may indicate that issues are being created with inflated priorities and then quietly downgraded, or that sprint pressure is causing retrospective deprioritisation to avoid accountability for missed targets.

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.