Tips & Best Practices

Capacity Planning

• Run a capacity check before every sprint planning session - the Assignee Capacity tab shows carryover load in real time.
• Use the Assignee Capacity tab before sprint planning to spot over-allocated team members before commitments are made.
• Save your plans for recurring planning cycles - don't reconfigure from scratch each sprint.
• Monitor Status Aging weekly - issues stuck in "In Review" for 5+ days are a reliable bottleneck indicator.
• Use Teams in the Capacity Planner - team-level grouping gives leadership a rolled-up view without reviewing each individual.

Time Tracking

• Log daily, not weekly. End-of-week logging is less accurate and harder to reconcile with actual Jira issue work.
• Use Time Categories to split time between Development, Meetings, Code Review, and QA - this makes reports much more useful for analysis.
• Use My Calendar to identify days with no logged time before the weekly approval window closes.
• Create Billing Accounts only if you have client billing needs - skip this feature if billing categorization isn't required.
• Set Date Range first before loading any report - the app requires a project and date range to load data.

Portfolio Management

• Save portfolios immediately after creating them - unsaved portfolios are lost on navigation.
• Use JQL for complex portfolios - manual filters are easier to set up but JQL is more powerful for cross-project scenarios.
• Set sharing roles deliberately - a portfolio's View/Edit/Edit generators/Control roles control who can see and change it; don't leave a shared portfolio on a default that's broader than you intend.
• Use the Treemap and Pie Chart views for executive stakeholder reporting - they convey health at a glance without detail overload.
• Use the Gantt panel from Table view for timeline planning - it isn't a separate view in the view switcher.

Backlog Prioritization

• Use one scoring template consistently within a team or planning cycle - changing templates mid-cycle makes comparison impossible.
• Keep metric definitions clear in the template description so all team members score with the same interpretation.
• Save commonly used views for recurring backlog reviews - views preserve column layout, filters, and sorting.
• Use the Priority Matrix alongside the table - the visual quadrant view often reveals patterns that aren't obvious in a sorted list.
• Save a report before each sprint planning session to create a historical record of how you prioritized.

Team Management

• Keep team membership current manually - teams are built from individual user search, not Jira Group auto-sync, so membership doesn't follow Jira group changes automatically.
• Create Programs for leadership capacity reviews - rolling up Teams → Program gives directors aggregate data without per-person detail.
• A team can belong to only one program - restructure programs if teams move between departments.

General

• Ask your admin what role or Permission Role you hold before contacting support about missing features - most "missing" features are permission-based, and there's no self-service "My Permissions" screen.
• Narrow your date ranges for large projects - loading 10,000+ issues takes time; use filters to keep datasets focused.
• Refresh manually to see changes made by other users - the app does not push live updates.