Coordinate infrastructure changes with clear dependencies and delivery checkpoints.
Coordinate infrastructure changes with clear dependencies and delivery checkpoints.
An environment upgrade may depend on network access, a validated configuration and another team’s work. Record the typed issue relationships and keep each referenced project within the approved access boundary. Resolving one blocker must not clear every dependency on the change.
Infrastructure work often competes for the same review queue. Apply effective WIP limits to all applicable board views, including events and bulk moves. A filtered screen cannot make an occupied review slot appear free to the transition service.
Use a consistent estimate unit and freeze commitments when the sprint starts. At closure, record incomplete and removed work before rolling it forward. This keeps planning history useful even when the current issue moves to a later iteration.
Preserve iteration evidence
Expose dependencies before execution
Control review capacity
Same records, same gates. The configuration changes how the process runs for this team.
Visible to: Project Lead / Product Owner, QA / Tester, Scrum Master / Iteration Manager. Visibility does not establish approval authority.
| Approval Number | Issue | Transition | Requested By | Requested At |
|---|---|---|---|---|
| TA-76326 | ISS-6796 | WT-7164 | YF | 29 Sep |
| TA-28936 | ISS-5625 | WT-7399 | GN | 16 Sep |
| TA-74461 | ISS-1532 | WT-5486 | PN | 10 Sep |
| TA-10206 | ISS-2383 | WT-6069 | XC | 06 Sep |
| TA-51614 | ISS-6360 | WT-7530 | MX | 19 Sep |
| TA-42088 | ISS-1794 | WT-5612 | WX | 22 Sep |
| 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 |
Runs the Sprint cadence and the Board. Owns ceremonies (planning, standup, review, retro), WIP discipline, and the burndown.
Delivery contributor. Works assigned Issues, transitions Status, logs work, comments, attaches files, opens PRs that auto-link back.
Owns the Project end-to-end — backlog priority, release planning, estimate overrides, scope decisions. The DRI for the product the Project ships.
Move work through explicit states while respecting the team’s review gates and work-in-progress limits.
Connect repository evidence to a reviewed release scope without confusing a merge with a deployment.
Plan each iteration around a visible goal and preserve what the team committed to at the start.
Organise product and IT work by project, component and a clear backlog priority.
Review epic progress and iteration history using dated evidence and consistent estimate units.
Keep reported evidence, investigation and independent quality decisions attached to the issue.
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.
Per Project, per IssueType: distribution of elapsed time Created → ResolvedAt (lead time) and StartedAt → ResolvedAt (cycle time), with p50 / p90 markers. Diagnoses queue length and review-stage delays by status.
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.
Click Start now, then use Proto to configure your project roles, issue workflow, board limits and repository connections.
Related questionOnly 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 questionNo. Closing outcomes are frozen before current issues move. Later estimates, assignments and status changes cannot rewrite closed history.
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.
