...
As described in the Step-by-step guide above, you can download a file that contains all custom field context details for a deployment. Customize this file or create your own, and make sure it's in JSON format. Refer to our guide for transformation listing requirements.
Using the JSON transformations, you can map a source context to a selected destination context one or create a mapped source context as a new one on the destination. This allows you to Read more about the context transformations you can perform. This way, you can change existing context mappings, set a mapping for new contexts, or transform a mapped context to a new destination context. You can find information about the logic of what happens with the source and destination context configurations in the Use cases for context transformationssection.
...
Mapping a source context to a chosen destination context by idID
| Code Block | ||
|---|---|---|
| ||
{
"source": {
"id": "customfield_10000",
"name": "Custom Field",
"type": "com.demo.text"
},
"children": [
{
"contexts": [
{
"source": {
"id": "10000",
"name": "Name",
"projectKeys": [
"Demo",
"Doc"
],
"global": true
},
"destination": {
"id": "10100"
},
"transformation": {
"id": "10102"
}
}
]
}
]
} |
...
Mapping a source context to a chosen destination context by idID
| Code Block | ||
|---|---|---|
| ||
{
"source": {
"id": "customfield_10000"
},
"children": [
{
"contexts": [
{
"source": {
"id": "10000"
},
"transformation": {
"id": "10102"
}
}
]
}
]
} |
...