Relativity - AI Powered Estimation and Forecasting

AI-powered relative estimation and forecasting for Jira Cloud

View the Project on GitHub angad2010/relativity-docs

Relativity — Documentation

Getting Started

What is Relativity?

Relativity is an AI-powered relative estimation and forecasting app for Jira Cloud. It analyzes your completed epics to discover natural effort bands, forecast delivery timelines, and help your team make data-driven planning decisions.

Installation

  1. Install Relativity from the Atlassian Marketplace
  2. Navigate to Relativity from the Apps menu in Jira
  3. Enter a JQL query that returns your completed epics (or pick a template)
  4. Click “Analyze Epics” to run the AI analysis

System Requirements


Features

Effort Band Analysis (Free)

Relativity uses AI-powered pattern recognition to detect natural effort bands — groupings of similar-sized epics that emerge from your actual delivery history.

How to use:

  1. Enter a JQL query like issuetype = Epic AND status = Done AND resolved >= -6m
  2. The AI analyzes child issues, sums story points, calculates Epic Cycle Time, and computes complexity
  3. Natural effort bands are detected automatically
  4. Each band shows: story point range, average cycle time, velocity, complexity tier, and predictability score

Controls:

Compare Epics (Free)

Click “Compare” on any epic card to add it to the comparison panel. Compare epics across bands with aggregate stats:

What-If Simulator (Free + Standard)

Plan future work by exploring how different story point estimates would track against your historical data.

How to use:

  1. Drag the slider or type a story point value
  2. Use quick-pick chips to jump to a band midpoint
  3. See the matching band with delivery forecast and confidence range
  4. Review the cycle time distribution bar (p10 through p90)

Standard tier adds: 5 most similar past epics with actual cycle time, velocity, and complexity data.

AI Insights (Standard)

A bird’s-eye view of your delivery intelligence:

AI Prediction (Standard)

Get a live AI-powered delivery prediction for any epic — in-progress or completed.

How to use:

  1. Switch to the AI Prediction tab
  2. Enter any epic key (e.g., PROJ-123)
  3. Click “Track”
  4. See: epic status, progress bar, completed/total story points, days elapsed, velocity
  5. AI matches the epic to a historical band and shows: expected cycle time range, projected total story points, and tracking status (Ahead / On Track / Behind)

Saved Analyses (Standard)

Save analysis results to revisit later. Load any saved analysis to see the full results without re-running the query.

Trend Tracking (Standard)

Track how effort bands shift over time across multiple saved analyses. Stable lines suggest consistent sizing patterns. Converging lines indicate improving estimation consistency.

Scheduled Analysis (Standard)

Set up automated weekly or monthly analysis runs on saved JQL queries. Results are saved automatically for trend tracking.


Key Concepts

Effort Bands

Natural groupings of epic sizes identified by AI-powered analysis. Each band represents a cluster of epics with similar story point totals. Bands are not manually defined — they emerge from your actual data.

Epic Cycle Time

The number of days from when the first child issue starts work to when the last child issue completes. Calculated from Jira status transitions (when issues move to In Progress and Done).

Complexity Score

A 0–100 score computed from four signals: number of child issues, comments, links, and commits. Weights are adaptive — signals with more variance in your dataset get higher weight because they differentiate complexity more effectively.

Velocity

Story points delivered per day. Calculated as total story points divided by Epic Cycle Time. Higher velocity means faster delivery throughput.

Predictability

How consistent both story point sizing and delivery time are within a band. Uses adaptive AI weights — the signal (sizing spread vs cycle time spread) that varies more gets more weight. High predictability means you can reliably predict both size and delivery time for epics in that band.

Needs Review

Completed epics that took longer AND were more complex than typical for their band. These are worth investigating to understand what caused the deviation — scope creep, blockers, dependencies, or other factors.

Delivery Health Score

An AI-weighted composite score (0–100) measuring overall delivery health across four dimensions: predictability, risk rate, velocity consistency, and complexity balance. Weights adapt to which factors vary most in your data.


Pricing

Feature Free Standard
Effort band analysis Included Included
What-If Simulator (forecast + band match) Included Included
Story Points / Cycle Time toggle Included Included
Sensitivity slider Included Included
Search, sort, compare epics Included Included
Interactive guide Included Included
AI Insights (Health Score, Findings, Recommendations) Included
Similar Past Epics in Simulator Included
AI Prediction (live epic tracking) Included
Save and load analyses Included
Trend tracking over time Included
Scheduled analysis Included

Standard tier: $2/user/month with a 30-day free trial.


FAQ

What JQL should I use?

Start with: issuetype = Epic AND status = Done AND resolved >= -6m ORDER BY resolved DESC

This returns all completed epics from the last 6 months. Relativity works best with 20–500 completed epics.

Why are some of my epics excluded?

Relativity only analyzes completed epics (Done/Closed status) that have child issues with story points. Epics without completed children or without story points are excluded with a warning.

How are story points calculated?

Story points are summed from completed child issues (issues with a Done status category). The story point field is auto-detected from your Jira configuration.

Can I use Relativity with non-Epic issue types?

Currently Relativity only supports Epics. If your JQL returns non-Epic issues, they will be excluded with a warning message.

Is my data sent to external servers?

No. All analysis runs within your Atlassian Forge environment. No data leaves your Jira instance. Relativity has read-only access and cannot modify your Jira data.

How does the AI work?

Relativity uses proprietary AI-powered pattern recognition to detect natural groupings in your delivery data. The analysis adapts to your specific dataset — weights, thresholds, and band boundaries are all computed from your actual delivery history, not predetermined rules.


Support


© 2026 Relativity Labs. All rights reserved.