Search “jira align enterprise insights” and every one of the top results is Atlassian’s own — help docs, product pages, support articles. What none of them answer directly is the question that actually drives people there: how do I see what this data looked like before, not just what it looks like right now? Three named Atlassian Community threads ask a version of exactly that — a baseline of the Program Board (2,435 views), historical data for a past quality check (1,911 views), and what the History tables’ date-range fields even mean (1,824 views) — and in each case, Atlassian’s own reply is some flavor of “query Enterprise Insights yourself.” This page pulls together what Enterprise Insights actually exposes, sourced from Jira Align’s own documentation and those named threads. Crosstown Tech has never run Jira Align and isn’t pretending otherwise.
Wait — is it “Jira Align” or “Atlassian Align”?
Briefly, because it affects what you search: every source this page cites — the Enterprise Insights docs, the Community threads, the database view names themselves — says “Jira Align,” not “Atlassian Align.” The naming drift that’s live elsewhere on Atlassian’s marketing page hasn’t touched the reporting layer. Full breakdown: What is Jira Align?
The one native answer: Program Increment scope change
Before reaching for Enterprise Insights, it’s worth knowing Jira Align does ship one built-in historical report. Per Jira Align’s own Program increment scope change documentation, a program-level report tracks features added to or removed from a PI against what was in scope at the start, with “a detailed list of features, categorized by when they were committed, added to, or removed from the PI” plus a chart of scope change measured in story points. If the only historical question is “has our PI scope changed,” this report answers it natively, no Enterprise Insights required — access it from a program’s Reports sidebar.
That’s the one exception. It doesn’t cover the Program Board specifically, it doesn’t let you pick an arbitrary earlier date to compare against, and it doesn’t extend to Epics, Themes, or anything above the PI level. For all of that, there’s exactly one path forward.
Enterprise Insights: the schema is documented, the questions aren’t
Enterprise Insights is not a feature you toggle on inside Jira Align’s UI — it’s a separate, read-only reporting database. Per Jira Align’s own “Get started with Enterprise Insights” documentation, it’s “a data mart of normalized and transformed Jira Align data,” hosted on Microsoft Azure SQL Server and “optimized for read-only operations,” built specifically to be queried with a modern reporting tool rather than browsed inside Jira Align itself. Atlassian’s own Enterprise Insights product page frames the pitch plainly: “go beyond the included reports in Jira Align” by connecting “your own visualization solutions, such as Tableau or Power BI, to browse your Jira Align data in one place.”
The part that actually answers “historical data” questions is Enterprise Insights’ set of History views — Feature History, Epic History, and equivalents for other work-item types. Each one stores every past state of an item as its own row, not just the current one. That’s the schema Atlassian documents. What it doesn’t do is tell you, in plain language, how to turn “every past state” into “the state as of a specific date” — which is exactly the gap the Community threads below are filling in Atlassian’s place.
Fact Valid From / Fact Valid To: the two columns that make it queryable
Every row in a History view carries two date columns — Fact Valid From and Fact Valid To — and understanding them is the difference between a query that works and one that silently double-counts. A user asked exactly what they mean in a 1,824-view Atlassian Community thread, having noticed that a record’s Valid From always matches the previous record’s Valid To, and that the most recent record’s Valid To is always the sentinel date 12/31/9999.
An Atlassian Team member’s answer: don’t filter on Valid From alone. To get an item’s state as of a given moment, the condition has to check both columns together — “greater than the Valid From AND less than the Valid To” — because more than one history row can exist for the same item on the same day if it was edited more than once. Get that wrong and a “state as of” query either returns nothing or returns two overlapping rows for the same day.
A separate, 1,911-view thread — “Obtain Historical Data for Quality Purpose” — shows what applying that correctly looks like in practice. The asker wanted to know how many Features had no Capability assigned as of a specific past date. An Atlassian Team member’s answer supplied a working SQL query against current_dw.Feature History, filtering to rows where the Capability foreign key was 0 (unassigned) and the Feature’s Fact Valid From/To range covered the target date — noting plainly that “filtering of dates can be a little tricky.”
That same technique isn’t limited to Capability assignment. Feature History carries a foreign key column for whatever a Feature is currently pointed at, including its Program Increment — so the identical Valid From/To filtering answers “which PI was this Feature assigned to on this date” or “when did this Feature’s PI assignment last change,” not just the Capability example the thread happens to use. Jira Align’s own schema documentation describes the columns; connecting them to the specific question you’re asking is left to you.
The Program Board baseline gap
The clearest example of “the schema exists, the report doesn’t” is the Program Board. In a 2,435-view thread titled “Baseline of the Program Board,” a user asked for a way to see what had changed on the board since the plan was set at the start of the PI — a two-point-in-time diff, not a running log.
Atlassian’s reply pointed to the board’s own History button, which lists every instance a card was moved, filterable by team. That answers “what moved and when” as a chronological feed, but it isn’t a baseline — there’s no single view that shows “the board as planned” side by side with “the board as it stands today.” The asker’s own follow-up in the thread confirms as much, and a suggested workaround — using the Roadmap’s “Detached Instance” feature to freeze a snapshot — comes with no confirmed way to generate an actual delta between two snapshots. If a true before/after Program Board view matters, it has to be built the same way as everything else here: pull the underlying Feature and dependency assignments from Enterprise Insights at two dates and diff them yourself.
The standing answer, in one line
Across all three threads, Atlassian’s own replies converge on the same answer: there’s no native report for this, so query Enterprise Insights’ History views yourself, in Power BI or Tableau, using Fact Valid From/To to pin down a point in time. That’s a genuinely different level of effort than clicking a built-in report — it means having someone who can write SQL against an Azure database, understands the Valid From/To pairing well enough not to double-count, and is willing to rebuild views like a Program Board baseline from scratch rather than finding them ready-made.
For organizations already running Jira Align at the scale it’s built for — hundreds to thousands of users, per Atlassian’s own sizing — that’s usually a solvable BI project, not a blocker. The friction is that Atlassian’s documentation describes the schema in detail and stops there; the actual question — “how do I get the specific historical view I need” — gets answered piecemeal, thread by thread, by Atlassian Team members typing out one-off SQL rather than by a documented pattern.
If you’re earlier in the Jira Align decision
This page assumes you’re already inside Jira Align and hitting the limits of its built-in reporting. If you’re still working out whether Jira Align is the right tool at all, what is Jira Align? is the starting point, Jira Align vs Jira clears up whether it’s a separate purchase (it is), Jira Align pricing covers what it costs since Atlassian won’t publish a number, and Jira Align hierarchy levels explains the organizational and work-item structures that Enterprise Insights’ History views are ultimately built around.