Status Transition truncated when exporting to Excel via plugin

[Meredith Weeman]

I have noticed an issue whereby the status transition data is truncated: not all status transition rows are being pulled out into Excel when using the Jira Cloud plugin for Excel. And I don't believe there is any other way to get this out of Jira (i.e., simply exporting from Jira?). For example, I have stories that started in New status then moved to Refinement > Dev Ready > etc. etc. but for no apparent reason or consistency, the status transition for some stories statuses are not coming out. There seems to be no consistency either - some stories all status transition history is pulled out, some start in the 3rd status, some in 4th, etc. Thanks! Meredith

[Meredith Weeman · Accepted solution]

I just wanted to close the loop, that after talking with Atlassian support, they indicate it looks like this happened due to recent changes in the way Jira returns elements from the work item changelog. Now, there is a hard limit of 40 entries (including status changes., field changes, etc.), and if the work item has more entries, it could be possible that the previous entries are not part of the 40 entries returned. The limit is for any field updates done for the work item. Status is one of the fields, but changes to other fields are included as well, like labels, description, dates, work logs, assignees, etc. Unfortunately, it's not possible to filter the history by field type so Jira returns the latest 40 entries, and the Jira Cloud for Excel app only shows the data related to the Status as per your configuration.

They have created the following feature request to improve this behavior when interacting with MS Excel/Google Sheets in case anyone wants to add themselves as a watcher / vote it up:

• API-768: Jira <> Sheets/Excel could not fetch all the changelogs

[Tomislav Tobijas]

Hi @Meredith Weeman ,

Has this just started appearing or has it been since start? In the past, I've seen some irregular behaviour when it comes to this app and sometimes it was resolved by itself (never this specific issue though)

As this is an official app you could also try reaching out to Atlassian Support to see if they can check what's going on in the backend.

Cheers,
Tobi

[Meredith Weeman]

Thanks! I had not seen this last time I ran this (in December), so just saw it about 2 weeks ago, across a few saved Jira filters. And thanks, I will try support!