# EASE-7073 Does the exalate support sync the linked issues in the same project?

**URL:** <https://community.exalate.com/t/ease-7073-does-the-exalate-support-sync-the-linked-issues-in-the-same-project/4521>\
**Category:** General Questions\
**Tags:** exalate, usecase, migrated\_question, inprogress\
**Created:** [November 4, 2024, 7:03am UTC](https://community.exalate.com/t/ease-7073-does-the-exalate-support-sync-the-linked-issues-in-the-same-project/4521 "2024-11-04T07:03:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![xl8bot](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/xl8bot/32/324_2.png) [@xl8bot](https://community.exalate.com/u/xl8bot)\
**Post date:** [November 4, 2024, 7:03am UTC](https://community.exalate.com/t/ease-7073-does-the-exalate-support-sync-the-linked-issues-in-the-same-project/4521/1 "2024-11-04T07:03:46Z")

</div>

_Originally asked by Helen Li on 22 December 2020 [(original question)](https://oldcommunity.exalate.com/questions/20123623)_

* * *

Dear sir,

I have a use case as below.

In the same project, there is a ticket A, then incoming a ticket B. A and B are the same tickets that we say tehy are the duplicated tickets.

We will link the ticket B to Ticket A by duplicates link type. Then we will working in ticket A, when any changed in ticket A, the ticket B will auto changed.

Does the Exalate can do this case?

Best regards,

Haihua Li

* * *

---

<div class="post-metadata">

**Author:** ![xl8bot](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/xl8bot/32/324_2.png) [@xl8bot](https://community.exalate.com/u/xl8bot)\
**Post date:** [November 4, 2024, 7:03am UTC](https://community.exalate.com/t/ease-7073-does-the-exalate-support-sync-the-linked-issues-in-the-same-project/4521/2 "2024-11-04T07:03:47Z")

</div>

_Answer by Helen Li on 23 December 2020_

Dear Sir,

I known how to sync it. We can use the connect button in the more drop down list of an issue.

But I have another question, i don’t want to connect it by myself but auto.

When I link the issues by duplicate link type, then it can auto trigger the connenction by reading the linked issue id? How to implement it? Any suggestion?

Best regards,

Haihua Li

* * *

#### Comments:

> **Helen Li commented on 23 December 2020**
>
> > Dear Sir,
> 
> Please give me some suggestion, thanks.
> 
> Best regards,
> 
> Haihua

> **Helen Li commented on 23 December 2020**
>
> > Still I found, the connect only can connenct 1 ticket.  
> > I found another solution, but do not know where the code put?
> 
> [Connect multiple support issues to a single development issue](https://oldcommunity.exalate.com/questions/2592581/connect-multiple-support-issues-to-a-single-development-issue)_(old community)_

> **Francis Martens (Exalate) commented on 23 December 2020**
>
> > This is an interesting use case.  
> > Auto connect issues which are linked together using a connect operation.
> 
> It is a bit of a head-scratcher.  
> Note that you can connect by exalating and setting the issue.id in the firstSync section

> **Helen Li commented on 24 December 2020**
>
> > Is there any sample code about connect script?

> **Francis Martens (Exalate) commented on 05 January 2021**
>
> > It is a bit more advanced setup - but certainly feasible
> 
> - Assume that you have issue A1 exalated to B1
> - Assume that you need to connect A2 to B1
> - Exalate A2 to B adding a property (customKey, customField) indicating that it needs to be connected to B1
> - Use a function like [getLocalIssueFromRemoteUrn](https://docs.idalko.com/exalate/x/EAFzAg) to find the issue id of B1
> - Use following code to connect
> 
> ```auto
> issue.id = foundIssue.id
> 
> ```

> **Helen Li commented on 15 January 2021**
>
> > Thanks，I will try it. If success, I will share the code.