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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Change IDs not sequential in ChangeGroup table in Database

We create custom SSRS reports for our Jira instance using SQL procedures that we develop ourselves. We migrated to Data Center this summer (2021) and have noticed a particular issue with the change history table.

The proc in question is querying status changes and where we use the Change ID as the basis for the sequence of these changes. We've discovered recently that the change ID is not in sequence with the timestamp of the changes in the changegroup table (breaking the reporting logic).

Has anyone else come across this? Is it a new thing to do with Data Center or are sets of ChangeIDs reserved by the system?

1 answer

0 votes

This is one of the reasons you should not be using the database for reporting - it's not intended for it, and you've made an incorrect assumption about how it works.

The change id in the changegroup table is not intended to be any indicater of order, and absolutely won't be in some cases (one of which is simply "data center")

Your reporting should never have assumed that IDs are ordered by the date/time on the change history, they should be looking at the date/time itself for an order.  Or, better, not looking at the database at all.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events