Cross-project change history
With any-field transition and exclusion filters.
Shipped
In UndoTrail for Jira today:
With any-field transition and exclusion filters.
Saved views and shareable report links.
Reports of up to 150,000 changes, exported in chunks so the page stays responsive.
With a dry run and a conflict check.
Including custom fields and subtasks.
With per-project opt-out.
Across current and historical field values.
PDF export, scheduled reports and a Rovo agent.
Next
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.
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
Each of these was seriously considered. Two of them were actually built before we decided the trade was wrong.
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.
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.
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.
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
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.