PL-01
Item Stuck in Pre-Release Stage
Pipeline
Default severity: medium
ProcessOutputRisk
What it detects
An issue has been in a configured pre-release stage for longer than the configured warning and critical thresholds.
Detection formula
pre_release_stages = config.workflow.pre_release_stages // configurable list time_in_stage = today - last_transition_into_pre_release_stage IF time_in_stage > config.pipeline.warning_days // default: 30d THEN FLAG IF time_in_stage > config.pipeline.critical_days // default: 90d THEN CRITICALExamples in practice
- A team shows an issue has been in a configured pre-release stage for longer than the configured warning and critical thresholds while pre release stages is set to Configured per workspace.
- Example signal: An issue has been in a configured pre-release stage for longer than the configured warning and critical thresholds.
Suggested response
Unblock pre-release and carry-over items with clear ownership and planning labels.
Coaching playbook
Symptom
An issue has been in a configured pre-release stage for longer than the configured warning and critical thresholds.
Why it matters
When "Item Stuck in Pre-Release Stage" keeps appearing, the team is signalling a repeatable process gap. Left unexamined, the pattern hides where work really stalls and makes improvement metrics harder to trust.
What you can achieve
Unblock pre-release and carry-over items with clear ownership and planning labels.
Facilitation questions
- What system change would stop "Item Stuck in Pre-Release Stage" from firing again?
- What do the cited issues have in common — same root cause or same workaround?
- Who owns the two-week experiment and how will we verify on the next import?
Run this rule against your own tracker data with Flow Analyzer.