| Table of Contents |
|---|
Basic
...
behavior
Here is a description how normal synchronization process executes:
- You have issue in JIRA A instance, you click on create remote ( it can be made automatically when you set up the triggers in contract configuration e.g onCreatedIssue or onUpdatedIssue)
- The request is send to JIRA B instance to create issue ( corresponding to the contract, which caused the request )
- Issue is created, response to JIRA A is sent.
- Your issues are now synchronized.
Clone JIRA instance
Let's assume you already have issues on both JIRA instances, which you want to synchronize between instances but you don't want to trigger create new remote issues. In other words you want to synchronize issues that already exists.
...
What you need to do is: just add new entity to the database, which will correspond to your desired mapping.
Step-by-step guide
Glossary:
- <JIRA-A-DB> - is the pointer to the JIRA A database scheme
- {} - provide a value here
...
If you are trying to perform a more complex mapping and you struggle with that, contact with us!
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| hidden | true |
|---|
...