Note
We've packed up and moved from Confluence to Discourse to bring you a better, more interactive space. Out of courtesy we didn't migrate your user account so - you will have to signup again
The Exalate team will be on holiday for the coming days - returning Jan 4
Enjoy & stay safe
We are about deploying Exalate as means to synchronize issues from Jira Service Management (JSM) projects to Jira Software Projects (JSW) for we do not have classical 1st level support, the number of people possibly handling incoming requests (tickets and other types) is to high and so would be the costs for the appropriate number of JSM agents. The POC for this setup was made by end of last year with the help of some of your colleagues.
In the meantime Atlassian introduced organization details as kind of attributes to organizations in JSM. We want (and need) to have to set some of those details and put their values into custom fields when filling the fields of the destination issue in the Exalate synchronization. Alas the attributes can (as far as we know and have found out) only be retrieved from the API endpoint I provided. Its hostname is not that of the instance so the usual approach for the httpClient function to just provide the URL path does not apply and work here. So we are looking for a solution, ideally one where the Exalate apps authentication can be implizitely be used (as it is done with httpClient() so far).