Docs / Issue History Reports / What's New

What's New

What changed in each update of Issue History. The newest update is at the top.

Update 3 · October 2026

Issue History now shows every change, on every site.

New Changes column

  • The Changes column lists every field that changed in one cell, one line per field, for example "Status: To Do -> In Progress".
  • Add it with the Fields button next to the search. It is not on by default: your reports, their columns and the CSV stay as they were.
  • With the Changes column added, a report lists every change in its period, so it can show more issues and rows.
  • An issue created in the period is listed even if nobody has edited it since. Its row says "Created".
  • Long text changes, such as a description, show what changed word by word. Compare shows the whole text with the changes marked.
  • Compare is a button you can reach with the keyboard, and screen readers announce the removed and added words. In the issue tab and in gadgets it opens as a Jira dialog in the middle of the page.
  • Long values are cut in the table. The tooltip and the CSV have the full text.

Issue History tab in each issue

  • Each issue has an Issue History tab in its Activity section (under More), with the issue's whole history and the Changes column.
  • In the narrow side panel the changes are stacked. When the panel gets wider or narrower, the tab switches between the table and the stacked view.
  • An issue you have just created or edited shows up with its latest changes.
  • While it loads, the tab says "Loading the issue's history...". If it can't show the history, it says why.

Only the changes you want

  • Additional Criteria > Fields shows only the changes to the fields you pick, for example Sprint. The report says "Only changes to: ...".
  • Saved reports, shared links and dashboard gadgets keep the choice.
  • Pick Comments to see the comments, also when the Comments column isn't shown.

Large sites

  • The report searches only the issues updated in or just before its period, and reads their histories in bulk. Before, the issue limit counted every issue the search matched, so on a large site changes on older issues could be missing.
  • When the issue limit cuts a report short, the report says so under its dates.
  • If Jira doesn't send some of the issues, a message says how many are missing. Before, they were left out without a word.
  • One failed page of results no longer leaves the report empty.

Dashboard gadgets

  • A new gadget saved with the default period ("last 2 weeks") moves with the days. Before, it kept showing the two weeks before the day it was saved.
  • A moving period says so, for example "last 14 days and today".
  • The setup's JQL box keeps what you type.
  • Save checks the JQL with Jira first and shows that it is checking. If Jira can't run it, the setup stays open with Jira's message.
  • The setup fits a narrow gadget, the period calendar too, and its pop-ups are no longer cut off.
  • In a narrow gadget the Updated Fields button and the period dates are no longer cut (dates read like 10/15/26).
  • A Project, Issue Type or Status picker you have cleared reads "All" again.

Story Points and number fields

  • An issue without a Story Points estimate has an empty SP cell in the report and in the CSV. A real 0 stays 0.
  • The same goes for every number custom field: an empty field is an empty cell, as in Jira's own CSV export.
  • An issue without a time estimate has empty Original and Remaining cells, not 0h.
  • Before, an empty value showed 0, so COUNT, AVERAGE and MIN in a spreadsheet counted it. If you build on the CSV, these results can change. SUM stays the same.

Other changes

  • A custom field column, for example Story Points as a custom field, shows its changes. Issues whose only changes are to such a column are listed.
  • The Original, Remaining, SP and Parent columns show their changes, and each row shows the value of its time. Before, they showed today's value in every row.
  • An empty time in a change reads "-", for example "- -> 2h", not "Null".
  • The app no longer stays blank on sites with time tracking turned off. If the settings your Jira admin saved can't be read, the report uses the default settings and says so.
  • The report loads even when Jira refuses one of its lists (statuses, issue types, projects or filters).
  • An issue whose history holds a deleted status or priority keeps its rows.
  • When Jira can't run a search, the warning says why.
  • The Share Link dialog has a Copy button. A shared link whose JQL has a "%" opens.
  • If your saved reports can't be read, the Saved Reports dialog says so instead of "No Saved Reports". Deleting a report keeps one you saved in another tab.
  • A double click on Yes when exporting starts one export.
  • A CSV cell longer than a spreadsheet cell can hold (32,767 characters), such as the change of a very long description, is cut to fit, and its end says how long it was.
  • A table wider than its frame has a scrollbar right above it, not only under the last row.
  • The first load is faster: the JQL editor loads only when you switch to JQL search.
  • An empty priority no longer shows a broken image.

Update 1 · October 2026

Issue History now comes from Votazz.

Issue History has the Votazz logo and icon. Documentation opens docs.votazz.co, and Contact Us writes to support@votazz.co. These links and the issue keys in the report open again.

Saved reports

  • If Jira doesn't answer while you save or delete a report, nothing is changed and you get a message. Before, your other saved reports could be erased.
  • Reports you saved in the previous version of the app are listed again.
  • A link to a saved report that was deleted or belongs to someone else opens the default report with a note, instead of an empty page.

Period and times

  • The report covers exactly the days you pick.
  • Every time (the When column, the CSV export and the footer) is shown in your Jira time zone, like in Jira.
  • For moving periods such as "last 14 days" or "this week", "today" is your Jira date.
  • Before, the period was shifted by your browser's offset from UTC. West of UTC it took in the evening before the first day and left out the evening of the last day; east of UTC it was the other way round. "Last N weeks" without the current week could also end weeks ahead.
  • Because of this, counts near the edges of a period can change.

A misspelt JQL search shows Jira's error under the search box.

CSV export

  • Cells that look like formulas are kept as text.
  • Quotes in Jira text no longer break the columns.
  • A report that names a field your site doesn't have, for example a custom field deleted since, exports again.

Also

  • Warnings stay until you close them; confirmations go away by themselves.
  • A dashboard gadget whose setup was cancelled says how to set it up.
  • Times show two-digit hours.
  • Columns fit their content.
  • Only Jira admins can change the app's site-wide settings.
  • The footer shows the app's version.

Questions? See Help & Support or contact us.