# How to sync issues one to one between two another instance of jira (On premise)?

**URL:** https://community.exalate.com/t/how-to-sync-issues-one-to-one-between-two-another-instance-of-jira-on-premise/6490
**Category:** General Questions
**Tags:** onpremise-jira
**Created:** [June 27, 2025, 6:16am UTC](https://community.exalate.com/t/how-to-sync-issues-one-to-one-between-two-another-instance-of-jira-on-premise/6490 "2025-06-27T06:16:45Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Jillani\_Fazal](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/jillani_fazal/32/355_2.png) [@Jillani\_Fazal](https://community.exalate.com/u/Jillani_Fazal)
#### Post date: [June 27, 2025, 6:16am UTC](https://community.exalate.com/t/how-to-sync-issues-one-to-one-between-two-another-instance-of-jira-on-premise/6490/1 "2025-06-27T06:16:45Z")

</div>

We want to synchronize issues one to one between two another instance of jira (On premise), one way (sync issues from source instance to destination instance). I was testing sync with scripting and I noticed some problems in destination issues.

Symptoms

After synchronization issue:

1. In destination issue in Dates section fields “Updated” and “Resolved” are not correct. (See screenshots, source\_issue\_dates.png and destination\_issue\_dates.png)

2. In destination issue in history of issue, user, who made changes is not correct (See screenshots, source\_issue\_made\_changes.png and destination\_issue\_made\_changes.png ). Comments are correct.

How can I fix it?  
How can I mapping users in sync rules (regarding changeHistory) to resolve the problem?

* * *

Outgoing sync rules (part of rules) in the source instance:

replica.comments = issue.comments

replica.created = issue.created  
replica.updated = issue.updated  
replica.resolved = issue.resolved

replica.changeHistory = issue.changeHistory

* * *

Incoming sync rules (part of rules) on the destination instance:

issue.created = replica.created  
issue.updated = replica.updated  
issue.resolved = replica.resolved

issue.changeHistory = replica.changeHistory

issue.comments = commentHelper.mergeComments(issue, replica){  
it.executor = nodeHelper.getUserByUsername(it.author?.username)  
}

_(It was originally asked on the Exalate Support Portal on June 17, 2025)_

---

<div class="post-metadata">

### Author: ![Jillani\_Fazal](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/jillani_fazal/32/355_2.png) [@Jillani\_Fazal](https://community.exalate.com/u/Jillani_Fazal)
#### Post date: [June 27, 2025, 6:18am UTC](https://community.exalate.com/t/how-to-sync-issues-one-to-one-between-two-another-instance-of-jira-on-premise/6490/2 "2025-06-27T06:18:11Z")

</div>

For the users, used the following and it worked:

```
issue.changeHistory = replica.changeHistory.collect { change ->
def remoteHistoryUserKey = change.author?.key
change. **author** = nodeHelper. **getUser** (userMapping[remoteHistoryUserKey] ?: remoteHistoryUserKey)
return change
}

```

We checked easier option about sync Resolution Date and it also works without technical customfield.

1. Outgoing sync rule in source instance:

`replica.resolutionDate = issue.resolutionDate`

1. Incomig sync rule in the destination instance:

`issue.resolutionDate = replica.resolutionDate`

---

<div class="post-metadata">

### Author: ![Jillani\_Fazal](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/jillani_fazal/32/355_2.png) [@Jillani\_Fazal](https://community.exalate.com/u/Jillani_Fazal)
#### Post date: [June 28, 2025, 6:19am UTC](https://community.exalate.com/t/how-to-sync-issues-one-to-one-between-two-another-instance-of-jira-on-premise/6490/4 "2025-06-28T06:19:02Z")

</div>

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.