What historical Jira question is still the hardest for your team to answer?

[Petru Simion _Simitech Ltd__]

One thing I've noticed over years of working with Jira is that most questions are easy to answer when you're looking at the current state of an issue. The challenge starts when someone asks about the past—not just for a single issue, but across dozens, hundreds, or even thousands of issues.

That's usually when teams end up digging through change logs, exporting data, building spreadsheets, or manually piecing together information from multiple sources.

Examples I've seen come up include:

Point-in-Time States: What did this issue actually look like three months ago? Or what did an Asset object or schema look like before a major change?

Deltas & Audits: What changed between two specific dates? Which fields changed during a release or sprint? Who changed what, and when?

Time Analysis: How long was this issue waiting in a particular status? How long did it spend with a particular team or assignee?

I'm curious:

What historical Jira or Assets question is still the most time-consuming or frustrating for your team to answer today?

I'm not looking for feature requests. I'm more interested in real situations where you needed an answer and Jira didn't make it easy to get.

Does the challenge change as Jira instances grow, or do small and medium-sized teams run into many of the same problems?

Looking forward to hearing some real-world examples.

For context, I work on Marketplace apps focused on Jira history and reporting, including Issue History & Snapshots Reporter for Jira.

I'm asking because I'm interested in understanding which historical visibility gaps are still causing the most pain for Jira teams today.

[Bartek Szajkowski _ Orbiscend OU]

Hello @Petru Simion _Simitech Ltd__ 

Thanks for your discussion - I think it's a Great topic — these are exactly the questions that show where native Jira JQL falls short.

I represent Orbiscend OU, JQL Argon app provider (Powerful Search for Jira). JQL Argon 

From the JQL Argon app side, we can help with two of these:

1. Time Analysis — Argon's timeInStatus function lets you query directly in JQL how long issues spent in a specific status:

issue > timeInStatus("project = DEV", "In Review", "5d")

This works across hundreds of issues at once — no exports, no spreadsheets.

2. Deltas & Audits — changedBy and transitionedBy let you find issues where specific fields changed within a date range, and by whom:

issue in changedBy("project = DEV", "Status", "2024/01/01", "2024/03/31")

AND issue in transitionedBy("project = DEV", "Done", "2024/01/01", "2024/03/31")

3. Point-in-Time States - here I'm afraid we will not help you.

I hope my answer will be useful in your future development product.

Wish you all the best

Greetings
Bartek from Orbiscend OU

[Petru Simion _Simitech Ltd__]

Hi Bartek,

Thank you for the detailed response and for sharing those examples.

I agree that advanced JQL functions can help answer many Time Analysis and Audit-style questions, especially when the goal is to identify issues matching specific historical conditions or transitions.

The Point-in-Time State question is the one I find particularly interesting because it often comes up during audits, compliance reviews, incident investigations, or post-mortems, where teams need to understand not only what changed, but what the complete state of an issue or asset looked like at a specific moment in time.

I'm curious whether you've seen many requests from customers around historical reconstruction or point-in-time reporting, or if most of the demand you encounter is focused on search and filtering use cases.

Thanks again for contributing to the discussion.

Regards,
Petru

[Bartek Szajkowski _ Orbiscend OU]

Hi @Petru Simion _Simitech Ltd__ 

To be honest, we didn't have request for historical reconstruction reporting.

Mainly we base on filtering and searching issues. So this is core of our JQL Argon app. 

Greetings

Bartek