Give internal requesters visibility while keeping delivery decisions with the team.
Give internal requesters visibility while keeping delivery decisions with the team.
An employee can file an improvement or incident without receiving the entire project backlog. The reporter’s view includes their own issue and information expressly marked for them. Internal attachments, other reporters’ requests and detailed work logs retain their separate permissions.
A promoted helpdesk ticket or service incident retains its verified source identity. Authenticate the originating connection and route it to a permitted project and component. Retries reconcile the same issue instead of creating duplicate work. A sender’s email address does not grant project membership.
The team tracks progress through its configured workflow and shares the appropriate resolution with the requester. Required verification remains independent of the developer who prepared the work. A release cut preserves its scope while the operational deployment result stays with the connected environment system.
Keep requester access narrow · Bring service handoffs into one record
Communicate a reviewed outcome
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-388 | PRJ-2044 | Lowest iss-914 | IT-1227 | Lowest |
| IK-159 | PRJ-5411 | Low iss-143 | IT-7703 | Low |
| IK-405 | PRJ-1108 | Medium iss-521 | IT-8469 | Medium |
| IK-538 | PRJ-6119 | High iss-595 | IT-5339 | High |
| IK-163 | PRJ-7748 | Highest iss-407 | IT-5999 | Highest |
| IK-978 | PRJ-7861 | Critical iss-509 | IT-3144 | Critical |
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 |
Internal user outside the squad who needs to file Issues — IT help requesters, internal customers of an API team, stakeholders who hit a bug. Can create Issues and comment on own Issues; sees nothing else.
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, 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.
Per Project, per week: count of Issues moved to Status: Done bucketed by IssueType (Story / Bug / Task / Improvement). Pairs with created-count to surface bug pile-up vs. story delivery rate.
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 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.
