nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Changelog is giving story points and sprints related for most of the issues, but not all

Mateusz Wąsalski

Heyo,

I've got weird bug. I'm using this url "https://company.atlassian.net/rest/api/3/search/jql" to get all issues.

From changelog we are getting info about story points, sprints etc. but not for every issue it works. Not sure what to do with it, because we are checking story points change and we cannot do it for every single issues, because we have problem with some of them.

For example we have project 123, we are taking issues only from this project and issue tax-123 doesnt have any info about story points, sprint related to it and tax-234 has full history, first story point change, second, first sprint, second, third (because it's being moved to new sprint every two weeks) etc.

Did you face problem like above ?

Accepted answers

Arkadiusz Wroblewski

Hello @Mateusz Wąsalski

Jira’s changelog only tracks active modifications. If Story Points or Sprints were set during creation, imported, or migrated, no historical entry exists, and you must pull the values from the current fields response instead.

Check the History tab in the Jira UI. If the changes show up in the UI but not the API, check your pagination via isLast or switch to the bulk fetch endpoint using exact custom field IDs. Check that and go from there.

If you are quite sure this is a bug, raise a ticket with Atlassian Support and ask them to confirm whether it is actually a bug or intended behavior.

All comments

Arkadiusz Wroblewski

Hello @Mateusz Wąsalski

If you are quite sure this is a bug, raise a ticket with Atlassian Support and ask them to confirm whether it is actually a bug or intended behavior.

Fabio Racobaldo _Catworkx_

Hi @Mateusz Wąsalski ,

in changelog you have information about fields changed.

In your example, probably, tax-123 has been created with story point and sprint field valued (it will not appear in the changelog) and tax-234 had those field changed after creation. Isn't?

Please let me know,

Fabio

Mateusz Wąsalski

hey,

thanks for your comments

fotunately it was all about pagination, which I didn't even know might be a thing in changelog. Checked to earliest date in .json and it was way newer then i.e. story point change so pro tip for everybody: always check the dates

Mateusz Wąsalski

Even though for this small project we only needed the changelog to track changes, thanks to your comment I've modified the logic to also fetch issues where story points were added at the exact same time the task was created.

So, thank you!

Arkadiusz Wroblewski

@Mateusz Wąsalski

Yes, pagination is essential. While some instances are small enough to manage without it, in many cases, omitting pagination would lead to significant performance and usability issues. That's how it works, not only in Jira.

The most important thing is that you're happy with the solution you found.

Please also accept the answer that helped you, so that other users can find it more easily.

Have a great day! ☀️

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

issues

changelog