tfs.json
This JSON file holds an array of objects with each object representing a mapping used when data is sent from Easit GO to Azure DevOps.
| [
{
"identifier": "createTfsWorkItem",
"fields": {
"fieldNameInDevOps1": "${propertyNameValueFromEasitGOSentToDevOps1}",
"fieldNameInDevOps2": "${propertyNameValueFromEasitGOSentToDevOps2}",
"fieldNameInDevOps3": "${propertyNameValueFromEasitGOSentToDevOps3}"
}
}
]
|
Mapping object
Let us take a closer look at a more real mapping object.
Mapping
| [
{
"identifier": "createTfsWorkItem",
"fields": {
"System.Description": "${bps.description}",
"MyCompany.TFS.EasitGOID": "${bps.id}",
"System.Title": "${bps.title}"
}
}
]
|
identifier
Identifier defined in event handler in Easit GO that post data to the connector.
fields
Key value-pair of properties that we would to send to Azure DevOps. Name of key will be the property name sent to Azure DevOps, value is a mapping of itself to the data posted from Easit GO.
With the mapping above and response from Easit GO below, we get the result at the bottom.
Data from Easit GO
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19 | <EasitImport type="" version="1.0">
<Items>
<Item uid="965487">
<Properties>
<Property name="description">a description</Property>
<Property name="id">965487</Property>
<Property name="title">title in Easit GO</Property>
</Properties>
<Attachments/>
</Item>
</Items>
<ClientInfo>
<ClientName>Easit BPE</ClientName>
<ClientProperties>
<ClientProperty name="identifier">createTfsWorkItem</ClientProperty>
<ClientProperty name="initializedByXmlExport">MCwCFHNcPkffg/Elwb8ZeIuQ/IeNwgB6AhQUy2AizQfpVxHVWnIkaXpqO079GQ==</ClientProperty>
</ClientProperties>
</ClientInfo>
</EasitImport>
|
Result
| [
{
"identifier": "createTfsWorkItem",
"fields": {
"System.Description": "a description",
"MyCompany.TFS.EasitGOID": "965487",
"System.Title": "title in Easit GO"
}
}
]
|