̽»¨ÊÓƵ

The Capacity Planner & Insight module gives program managers and delivery leads a single place to forecast resource availability, allocate work, and detect over-commitment before it becomes a delivery problem. A named planning canvas with Gantt calendar view lets teams book issues to specific members across a planning horizon, with a Holiday Calendar feeding into capacity calculations so availability figures reflect actual working days - not theoretical headcount. Four analytics tabs — Team Allocation, Assignee Capacity, Deadlines & Risk and Status Aging — surface workload distribution, per-person utilization percentages, overdue issue rankings by risk level, and workflow bottlenecks from a single interface. Reusable saved plan configurations cut setup time for recurring planning cycles like sprint planning or quarterly resource reviews.

The Time Tracking module gives Jira teams a complete toolkit to log, view, and report on time without leaving Jira - no external tools, no manual spreadsheets, no end-of-week memory gaps. Team members can log time through a calendar view with drag-and-drop entries, a per-issue start/pause/stop timer embedded directly on every Jira issue panel, or a full log time modal with billing account selection and custom fields. A dedicated report builder generates nested, grouped timesheet reports with advanced filters, and every view exports to formatted XLSX with frozen panes and color-coded headers. Billing accounts, Time Categories (split a single entry across Development, Code Review, or Meetings), and custom worklog fields make the data directly usable for client invoicing, project accounting, and compliance reporting.

The Portfolio Management module aggregates work items from across multiple Jira projects into unified portfolio views, giving executive leadership and program managers a single source of truth for delivery health and strategic progress. Teams define portfolio scope through manual filters, saved Jira filters, or full JQL queries - then analyze it through six visualization modes: Gantt, Treemap, Board, Pie Chart, Table Tree, and Tree Graph. The Gantt view supports four dependency types (FS, SS, FF, SF), critical path highlighting, and drag-to-reschedule - giving delivery teams real-time schedule control without leaving Jira.

The Backlog Prioritization module replaces subjective ranking with a structured, auditable scoring framework applied directly to Jira issues - so every item in the backlog has a score, and every score has a record. Teams choose from built-in methods - ICE, RICE, WSJF, Value vs. Effort - or build custom templates with their own metric types including Number, Star Rating, Dropdown with scored options, Effort estimate, and native Jira fields. Scores calculate automatically as users edit metric values inline in the table, and every change is tracked in a per-issue change history log — giving teams a defensible record of prioritization decisions for any stakeholder review or audit. A Priority Matrix plots issues on a 2D scatter chart with configurable axes, and the full ranked backlog with all metrics exports to CSV for use as sprint planning input.

The app includes three supporting capabilities that tie the four core modules together: advanced reporting, Teams Management, and Role-Based Access Control with a full audit log. The reporting layer spans all modules — timesheet reports with nested grouping and XLSX export, Capacity analytics tabs with CSV export, and Portfolio views exportable as PNG for stakeholder decks. Teams Management lets organizations define team structures (Program → Teams → Members) that are referenced across Capacity, Time Tracking, and Portfolio workflows - with Jira group import keeping membership current automatically. RBAC uses a two-role model (Global Admin and Member) tied directly to Jira's user management, with a full Audit Log recording every role change - actor, timestamp, action, and affected user - filterable by date and searchable by name.