Keep product priorities, engineering work and release evidence connected.
Keep product priorities, engineering work and release evidence connected.
A product team can receive reports from internal customers while protecting its engineering discussion. Reporters see their own issues and deliberately shared evidence. Product owners triage the backlog by component and priority before work is selected for a sprint.
A merged pull request supplies code evidence. The issue still follows its configured workflow, including independent QA when required. Verified repository and branch identity prevent an unrelated merge event from moving a card. Preserve the required checks and gate result with the issue revision.
A version includes the completed work accepted into its frozen release scope. Unfinished work is moved through an explicit planning decision. The deployment platform supplies the separate environment outcome; release-note generation alone does not prove a deployed product.
Turn feedback into scoped work
Separate merge and verification
Review the release cut
Same records, same gates. The configuration changes how the process runs for this team.
| Issue Key | Project | Title | Severity | Reporter |
|---|---|---|---|---|
| IK-468 | PRJ-6674 | Lowest iss-966 | Sev1 | WS |
| IK-574 | PRJ-9723 | Low iss-123 | Sev2 | UC |
| IK-773 | PRJ-8533 | Medium iss-319 | Sev3 | YR |
| IK-981 | PRJ-5727 | High iss-188 | Sev4 | NP |
| IK-642 | PRJ-7482 | Highest iss-934 | Sev1 | BA |
| IK-821 | PRJ-5540 | Critical iss-685 | Sev2 | NZ |
| Issue Key | Project | Title | Issue Type | Priority |
|---|---|---|---|---|
| IK-924 | PRJ-5787 | Lowest iss-186 | IT-1613 | Lowest |
| IK-499 | PRJ-2877 | Low iss-390 | IT-5179 | Low |
| IK-526 | PRJ-8052 | Medium iss-629 | IT-8682 | Medium |
| IK-745 | PRJ-9035 | High iss-655 | IT-9168 | High |
| IK-631 | PRJ-5950 | Highest iss-992 | IT-5996 | Highest |
| IK-912 | PRJ-8743 | Critical iss-679 | IT-2638 | Critical |
| Issue Key | Title | Issue Type | Priority | Parent Epic |
|---|---|---|---|---|
| IK-556 | Lowest iss-657 | IT-3797 | Lowest | EPC-5237 |
| IK-365 | Low iss-639 | IT-7722 | Low | EPC-2365 |
| IK-758 | Medium iss-304 | IT-3806 | Medium | EPC-3817 |
| IK-221 | High iss-494 | IT-9562 | High | EPC-4666 |
| IK-380 | Highest iss-910 | IT-4651 | Highest | EPC-9960 |
| IK-966 | Critical iss-851 | IT-4743 | Critical | EPC-5029 |
Owns the Project end-to-end — backlog priority, release planning, estimate overrides, scope decisions. The DRI for the product the Project ships.
Delivery contributor. Works assigned Issues, transitions Status, logs work, comments, attaches files, opens PRs that auto-link back.
Quality role. Files and verifies bug Issues, transitions Issues through the verification gate, signs off on InReview → Done for Bug-type Issues.
Connect repository evidence to a reviewed release scope without confusing a merge with a deployment.
Keep reported evidence, investigation and independent quality decisions attached to the issue.
Organise product and IT work by project, component and a clear backlog priority.
Move work through explicit states while respecting the team’s review gates and work-in-progress limits.
Review epic progress and iteration history using dated evidence and consistent estimate units.
Plan each iteration around a visible goal and preserve what the team committed to at the start.
Per Project: Backlog count by IssueType, by Priority, and by ParentEpic; share of Backlog rows missing required Estimates (per IssueTypes.RequiresEstimate); share missing FixVersion. The Product Owner's grooming worksheet.
Per Version: total Estimate vs. CompletedEstimate, projected ReleaseDate using the TeamVelocity trailing-3 average against remaining scope, and the per-Epic contribution. Surfaces at-risk releases ahead of cut date.
Per Project, per Sprint: CommittedPoints vs. CompletedPoints vs. Carryover, with the trailing-3-sprint average overlay. Drills into the per-Issue contribution list for any selected Sprint. The Scrum Master's ceremony report — read at sprint review and retrospective.
Only a permitted workflow transition can complete it. Required QA, dependency and WIP checks still apply to authenticated merge events.
Related questionChanges need the declared Admin and Project Lead review plus a valid mapping for active issue states. Earlier issue history keeps its original context.
Related questionThe transition checks the effective limit atomically. A second concurrent move cannot claim the same final slot, and lowering a limit keeps existing work visible.
Related questionNo. Closing outcomes are frozen before current issues move. Later estimates, assignments and status changes cannot rewrite closed history.
Related questionReporters see only their filed issues and comments or attachments expressly marked ReporterVisible. Internal discussion remains within the project audience.
Related questionIt records the reviewed release scope and source revision. The deployment platform provides the separate observed environment outcome.
Related questionConfigure one estimate unit for the project and its sprint reports. Mixing units would make commitment and velocity comparisons unreliable.
Related questionKeep product priorities, engineering work and release evidence connected.
Coordinate infrastructure changes with clear dependencies and delivery checkpoints.
Give internal requesters visibility while keeping delivery decisions with the team.
