To answer your question - you might have a look at the issue history lite which was introduced in june. We have 0 experience with it, so it is a wild guess
As I understand it, you would like to have a list of all the changes over all the issues that exalate touches?
We are planning for an audit feature which would provide this information.
This is still in its inception phase, so any suggestions for the audit functionality is welcome
Hi Francis,
Thanks for your response. I think this would primarily be helpful when first getting started with Exalate - it will help to build trust that the platform is sync'ing everything it should.
Re: functionality, I am picturing:
It would be nice if the audit log included clickable links for the local issue, so that I could quickly reach an issue of specific interest.
Sounds like a feature request 
Audit logging is in our roadmap, but we first need to move a mountain before we get to it.
Hey, Stephen Sayler , Javier Marcos please also consider the solution suggested here:
News feed for ongoing Exalate updates
here's the video:
Happy Exalating!
Serhiy Onyshchenko that solution looks good to me. i don't think i'll take the time to implement it, as it looks quite advanced and i'd rather not change our scripts.
we're still happy customers of Exalate, although it took a long time and a lot of effort to achieve a delicate balance between it and Jira Automation. our main pain point has been "thrashing" when an Exalate sync triggers a Jira automation in the other instance, causing newer values to be overwritten with older ones. since Exalate sends the entire view model across whenever an issue update happens, we have to be very careful in designing our automation triggers to prevent thrashing.
in some cases, we've implemented a webhook step in Jira Automation (http://httpbin.org/delay/5) that essentially pauses the automation for 5 seconds before implementing its action. generally when everything is running well this allows Exalate enough time to sync all the necessary changes and prevent Jira Automation from sending an old view model back.
My setup: I have 2 local projects, one with historical tickets and the other one will be the "destination" project. I have synced both, but the History information from the first one does not shows in the second one. Is there a way to keep the History from all tickets into the new tickets?
Also, I see that Comments from old ticket is shown in the new one, but the comment date is not correct, it is instead the "new ticket_creation date" (sort to call it) for all the comments. Is there a way to preserve the comment date also?
thank you
Hi Javier Marcos
This looks like a new question - can you create it as such?
btw - have a look at How to synchronize issue change history in Jira Server for details on the issue history sync.
I also need something similar... Hoping they release something to provide this information to users. Did you ever find a workaround? Stephen Sayler
Kaleigh Garcia yes, via Jira's Slack automation. I don't have a feed specific to Exalate (which may be possible) but I do see Exalate's activity in line with regular human driven activity, which has been good enough.
Jira Automation has a nice audit log feature, maybe Exalate could implement something along those lines.