1 answer
- 10-1
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
- Helen Li
Dear Sir,
Please give me some suggestion, thanks.
Best regards,
Haihua
- Helen Li
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
- Francis Martens (Exalate)
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
Is there any sample code about connect script?
- Francis Martens (Exalate)
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 to find the issue id of B1
Use following code to connect
issue.id = foundIssue.id
- Helen Li
Thanks，I will try it. If success, I will share the code.
Add your comment...
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