Confluence has been updated to ver 6.15.9. In case of any troubles, please contact infra team.
So you want exalate to create the organizations on the receiving side? We have this guide on how to sync the field by name but it wouldn't create a new organisation, let me know if that's enough.
The ideal case would be to automate the organization creation, however we could deal with having to create them manually on both sides as long as they are automatically synched for each issue.
As a summary of the use case, we are trying to create a 2nd Jira instance for certain customers due to branding issues (basically, they should operate with a different url than our base one). We would like to keep working on our instance and let the customers use the new one. If a customer creates a ticket, we should receive it with the right organization set on our instance, and the other way around, if we create a ticket with an organization, it should be created on the new branded instance with the same organization.
Hope it makes sense.
I have updated the docs on page: https://docs.idalko.com/exalate/display/ED/How+to+sync+Service+Desk+Organization+field+on+Jira+Cloud . Now the scripts provided there should sync the organization field (matching by name) between two Jira instances. Let me know if it works for you.
© 2019 Exalate. All rights reserved.