What is coming, and what is not

Most roadmaps are a wish list. This one includes the features we chose not to build and why, because that is usually the more useful half.

Shipped

In the product today

In UndoTrail for Jira today:

Cross-project change history

With any-field transition and exclusion filters.

Table and activity views

Saved views and shareable report links.

Streaming CSV and Excel exports

Reports of up to 150,000 changes, exported in chunks so the page stays responsive.

Revert and bulk revert

With a dry run and a conflict check.

Deleted work item capture and restore

Including custom fields and subtasks.

Comment history and viewer history

With per-project opt-out.

Secrets and PII scanner

Across current and historical field values.

Dashboard gadgets

PDF export, scheduled reports and a Rovo agent.

Next

What we are working on

Time in status

In development: Working-hours arithmetic that survives daylight saving, half-hour time zones and holidays, with cycle and lead time. The engine is built and tested; it is waiting on the first release settling down.

Jira Product Discovery coverage

Being tested: Verified on Software, Service Management, company-managed and team-managed projects. Product Discovery is untested and we say so rather than implying it works.

Decided against

Things we are not building, and why

Each of these was seriously considered. Two of them were actually built before we decided the trade was wrong.

A public REST API

Built, tested, and then removed. Adding a web trigger costs the app its Runs on Atlassian badge, which is the answer to most security questionnaires. We kept the badge. If a customer needs the API badly enough to trade that away, tell us.

A Confluence macro

Not built. It would add Confluence permissions to the consent screen that every Jira buyer sees, to serve a minority. Better as a separate listing later.

Attachment restore

Not built. Keeping copies of every attachment would quietly double a customer’s Atlassian storage bill. Field data is restored; attachments are not, and the documentation says so plainly.

Electronic signatures (21 CFR Part 11)

We ship tamper-evident signed exports and we never call them electronic signatures. Claiming Part 11 compliance needs a consultant, not a marketing page.

Ask

Need something that is not here?

Feature requests from paying customers move to the top of this list.

Tell us what you are trying to do rather than which feature you want, and we will often find you an answer that already exists.

Where to next

Back
to top