Introduction
Hello all,
The scene:
You have set up a succesful integration between Jira and Azure Devops. You want to integrate Sprints aswell. In Jira (any deployment), the sprints already exist, but in Azure Devops, it could be that the sprints don't exist yet.
Here is where Exalate can help you out. With the use of Exalate, we can create the new sprints in Azure Devops.
The first thing we need to do is to send out all the information about a Sprint from the Jira outgoing side.
If we have a look at the data that will be sent out to Azure Devops, this is how it looks:
If we add this line of code in the Outgoing Sync in Jira;
replica.customFields."Sprint" = issue.customFields."Sprint"
"customFields": { "Sprint": { "id": 10104, "name": "Sprint", "uid": "10104", "description": "Jira Software sprint field", "type": "SPRINTS", "value": [ { "id": "2", "state": "FUTURE", "name": "SprintTwo", "originBoardId": "7", "startDate": 1697476800000, "endDate": 1698686400000, "sequence": 2, "goal": "This sprint does not exist yet in ADO", "eventTriggerContext": {} } ] } },
Exalate will use this information to create a Sprint in Azure Devops.
In Azure Devops we need to add this code to the incoming sync.
Please be mindful that you need to change the projectKey after implementing following code;
Here is a video;
Thank you and happy exalating.
Questions
Recent Questions
- 0votes
- 0votes
- 0votes
- 0votes
- 0votes
- 0votes
- 0votes
- 1vote
- 0votes
- 0votes