Common Use Cases
1. Sprint Capacity Check Before Planning
Who: Engineering Manager When: Sprint planning day
Before committing to a sprint scope, the manager opens Capacity Analytics, sets the project and the upcoming two-week window, and reviews the Assignee Capacity tab. Three engineers have carryover issues with significant remaining estimates. The manager adjusts the sprint scope down by 20% before the planning meeting - avoiding the usual mid-sprint scramble.
Modules used: Capacity Analytics → Assignee Capacity tab
2. Identifying a Delivery Bottleneck
Who: Team Lead When: Mid-sprint check-in
The team's velocity feels off but no one can pinpoint why. The lead opens the Status Aging Monitor for the current sprint window. Six issues have been in "In Review" for more than five days - all assigned to the same reviewer. The lead reassigns two reviews and unblocks the queue in one conversation.
Modules used: Capacity Analytics → Status Aging Monitor tab
3. Quarterly Backlog Grooming
Who: Product Manager + Tech Lead When: End of quarter
Before the quarterly planning session, the PM creates a new prioritization plan in Backlog Prioritization. They score 40 backlog items using the weighted model (business value × 40%, effort × 30%, risk × 30%). The resulting ranked list becomes the input for the planning session, replacing a subjective spreadsheet that previously took two hours to prepare.
Modules used: Backlog Prioritization
4. Escalation-Ready Progress Report
Who: Director of Engineering When: Monthly executive review
The director opens Portfolio Management and exports a summary for three active projects. Each project shows delivery percentage, budget burn, and any flagged risks. The five-minute report replaces a 45-minute slide preparation exercise.
Modules used: Portfolio Management (PPM)
5. Time Audit for a Completed Project
Who: Delivery Manager When: Project retrospective
After a project closes, the delivery manager reviews time logs across all team members for the project duration. They compare estimated vs. actual hours per issue type to identify where estimation accuracy broke down - informing planning norms for the next project.
Modules used: Time Tracking
6. Onboarding a New Team Member
Who: Jira Admin When: New hire starts
A new developer joins. The Jira Admin opens RBAC → User Roles, finds the new user, and assigns the Member role. The developer now has access to log time, view capacity data, participate in backlog scoring, and view portfolio summaries.
Modules used: RBAC → User Roles, My Permissions
7. Flagging At-Risk Deadlines to Stakeholders
Who: Project Manager When: Weekly stakeholder update
The PM filters the Upcoming Deadlines & Risks tab to the current project and exports the list of overdue and high-risk items. They paste the table into the stakeholder update, with no manual issue hunting across the board.
Modules used: Capacity Analytics → Deadlines & Risks tab
8. Client Billing Report
Who: Consulting Delivery Lead When: End of billing cycle
The lead filters the Time Tracking Report Builder by Billing Account (one per client) and date range. The report exports to CSV for upload to the billing system. No manual aggregation required.
Modules used: Time Tracking → Billing Accounts → Report Builder