Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Is history id in changelog sequential?

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Nov 09, 2023

I want to make a polling system to find changed and created issues without webhooks.

I can get issues which are recently created/updated with JQL.

But I also have to identify whether an update already applied and not.

At first, I tried to use history id which I can find changelog. (changelog - histories - id)

"changelog": {
    "startAt": 0,
    "maxResults": 3,
    "total": 3,
    "histories": [
        "id": "10511",

 it seems to be sequential, but some histories which created recently have smaller id than histories which created older.

so I want to ask.

1. Is history id in changelog sequential?

2. If (1) is yes, what is the reason some history have smaller id than expected?

3. Is there any other indicators which I can identify the order of changes in jira issue?(excepted "Created" in changelog)


Thanks for reading.

1 answer

1 accepted

1 vote
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 09, 2023

Welcome to the Atlassian Community!

No.  It always increases, but it is not sequential.  The ID is global, so every change to every issue increases the id.

You can rely on the ID to say "an ID is a point in time - a lower ID is for a change that was made before this one, and a higher ID was a change after this", but that's it.  They can also skip numbers.

You should be reading created (and maybe last updated) date/time on the issues, and, in the history, the date/time stamp on the updates.   The ID can't tell you much.

Suggest an answer

Log in or Sign up to answer