What is the difference between changelog.history list and changelog.history.items

Steve Suranie March 21, 2024

I'm trying to figure out why a ticket would have multiple histories. I guess in my head a history object would hold all the changes to the ticket and the items would be each change with metadata like, date, user, what changed, etc. I'm using the API to crunch through tickets and reviewing their history entries and I am getting outputs like this: 


on 0: KAT-5615 history

on 0: 20

on 0: Item count for history entry 0: 1

on 0: Item count for history entry 1: 1

on 0: Item count for history entry 2: 1

on 0: Item count for history entry 3: 1

on 0: Item count for history entry 4: 1

on 0: Item count for history entry 5: 1

on 0: Item count for history entry 6: 1

on 0: Item count for history entry 7: 1

on 0: Item count for history entry 8: 1

on 0: Item count for history entry 9: 2

on 0: Item count for history entry 10: 1

on 0: Item count for history entry 11: 1

on 0: Item count for history entry 12: 1

on 0: Item count for history entry 13: 1

on 0: Item count for history entry 14: 1

on 0: Item count for history entry 15: 1

on 0: Item count for history entry 16: 1

on 0: Item count for history entry 17: 1

on 0: Item count for history entry 18: 1

on 0: Item count for history entry 19: 1

 

This just seems like a lot of extra work for us to dig through the history. In my specific situation I am writing a script for capacity planning so I am looking to see statuses and if any work was rolled over from the previous quarter. 

Could someone explain the logic of having multiple history objects? Especially since the timestamp is on the history object not the items. But a history object can have multiple items, which would seem to be multiple events, but they could not have both occurred at the same time. 

Thanks

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events