Are the changelogs in the bulk fetch api immutable

[Karthik Krishna Viriyala]

I want to use the changelog bulkfetch API https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-changelog-bulkfetch-post, in my application to sync issue changelogs. I wish to run the sync as a daily job. Since the bulk api returns the complete changelog history for a jira issue I am trying to figure out a way to avoid event duplication. I plan to check if a specific changelog id already exists in the db (so in the sample api response id = 10001 or 10002) then I will skip insert of these items. I want to understand if the specific changelog histories are immutable or if its possible more events maybe added to the same changelog history (i.e the items list of changelog 10001 or 10002 in the sample api response).

[Marc -Devoteam- · Accepted solution]

Hi @Karthik Krishna Viriyala 

You could have moe this depends on the amount of changes on an issue, so a 3rd change will create id 10003, etc.

The example output on the API documentation only show 2 changes made on that issue, so only 2 change log id's are in the output

[Karthik Krishna Viriyala]

Right i understand, but I want to understand is each change immutable? Or can more items be added to an existing change? So if i sync change of id 10002, do i need to worry about syncing it again later or can i safely ignore that and assume its up to date in my local db?

[Marc -Devoteam-]

Hi @Karthik Krishna Viriyala 

No the change id is set based on the change made on the issue (work item), so any change on the same issue done later will never be reflected within ID 100002 (example)

Each edit action will get is't own new ID.

[Karthik Krishna Viriyala]

Great. So it would be safe to assume that the change once persisted in db, can be ignored in further syncs and i wouldnt miss any events

[Marc -Devoteam-]

In short, Yes