Can sync replica.changeHistory in Jira Cloud?

Use Case
, , , ,
1

Originally asked by Alvaro Jardon on 25 November 2021 (original question)

Greetings,

I’ve seen you can access the changeHistory on Jira Server using replica.changeHistory , but it doesn’t seem to work on Cloud, is there a way to access the changeHistory of the issues on Cloud?

What I need to achieve is to exalate only the attachments added on a ticket during certain transitions.

I already am filtering attachments contained on a comment by role level and so on, but I need to filter specifically for transitions and not for be contained on a comment.

So getting the changeHistories and filtering for attachments added on the same changeHistory as specific status changes would do it, but it seems I can’t access to that either on Cloud.

Thanks in advance, kind regards,

Alvaro.

2

Answer by Tomasz Osojca on 07 December 2021

Referring to this page: https://docs.idalko.com/exalate/display/ED/Fields+and+entities+available+for+synchronization+in+Jira+Cloud

the following entity should be available for synchronisation for Jira Cloud

  • creation
  • resolution date
  • changeHistory

I did not manage to synchronize them.

Could someone explain if this is possible or the documentation is not correct?

Regards

Tomasz

3

Answer by Francis Martens (Exalate) on 25 November 2021

changeHistory is not supported in the issue entity on cloud
It is on the backlog among many other siblings

An alternative is to use httpClient and query the Jira directly for the changelog
(Here is the Atlassian doc)
something like

Untested

def response = httpClient.get("/rest/api/2/issue/${issue.key}/changelog")
debug.error("Response = ${response}")

Give it a try