Known Issues & Limitations

Very large histories in one page

Issue: If the issues on one page have an unusually large number of changes, loading can hit Forge's time limit and show "These issues have too much history to load in one go". Workaround: Choose a lower Limit and use Load more.

Very large PDF reports

Issue: The PDF is printed by your browser. Reports with several thousand changes run to hundreds of pages and can be slow to open. Workaround: Use Excel or CSV for large exports, or include only the Time in Status and Status Timeline sections in the PDF.

Business hours depend on the viewer's time zone

Issue: Business-hours calculations use each viewer's local time zone, so two people in different time zones can see different figures for the same issue. Workaround: Use calendar time when comparing figures across time zones.

Restore covers four fields

Issue: Restore is available for status, assignee, priority and summary only. A status Restore needs a workflow transition to the earlier status. Workaround: Change other fields in Jira directly.

Saved searches with people filters

Issue: When a saved or recent search with assignee or reporter filters is re-applied, those filters show account IDs instead of names. Workaround: The search itself is correct; re-select the people if you want to see their names.

What counts as history

Issue: History comes from Jira's changelog, which records field changes. Comments and work logs are not field changes and don't appear.