The Exalate team will be on holiday for the coming days - returning Jan 4
Enjoy & stay safe
In Jira, we can select multiple values for the field “Components” but in ADO, we can only select one component value. Because of this, we will have an issue with Exalate synchronization if more than one value is selected from the picklist in Jira.
Will Exalate allow to have multiple component values in ADO? In order words, can scripts be updated such that all the values from Jira sync to the ADO components field once we add the “Multivalue control” extension?
I did a quick test
Add following script to the incoming sync on the ADO side
// Set type name from source entity, if not found set a default
workItem.projectKey = "BugsRus"
workItem.typeName = "Issue"
workItem.summary = replica.summary
workItem.description = replica.description
workItem.attachments = attachmentHelper.mergeAttachments(workItem, replica)
workItem.comments = commentHelper.mergeComments(workItem, replica)
workItem.labels = replica.labels
workItem.priority = replica.priority
// Set the multivalue field
workItem.Components = "Legal;Operations"
The result is
Interesting to see that non existing values (Legal and Operations) are automatically added to the dropdown.So to answer the question - can Exalate deal with the multivalue control on the AD side ... Of course - YMMV (your mileage might vary) Have a coffee.
© 2019 Exalate. All rights reserved.