Troubleshooting issues for Azure DevOps integration with Agile Development
Summarize
Summary of Troubleshooting issues for Azure DevOps integration with Agile Development
This guide addresses common troubleshooting issues encountered during the integration of Azure DevOps with Agile Development 2.0. It provides actionable steps to resolve these issues effectively.
Show less
Key Features
- Export Action Issues: Ensure the custom map configuration is valid, required fields are mapped, and the project has the Enable Export checkbox selected.
- Sprint Import Issues: New iterations in Azure DevOps will not create sprints in Agile Development 2.0 until a work item is added. It's recommended to create sprints directly in Agile Development 2.0 for consistency.
- Assignment Group Population: Verify team associations and project integration settings to ensure assignment groups are populated correctly for stories and epics.
- Field Mapping Issues: Confirm custom field and state maps are configured to ensure data sync between Azure DevOps and Agile Development 2.0.
- Deletion Synchronization: Ensure the Can Delete field is set to true for the respective tables to synchronize deletions correctly.
- Project Importing: New Azure DevOps projects require manual discovery or scheduled jobs to sync with Agile Development 2.0.
- UI Action Errors: Known issues may cause errors during initial Connect, Disconnect, and Validate and Fix actions; retrying is recommended.
- HTML Field Mapping: Note that the Description field may render incorrectly due to unsupported HTML fields.
Key Outcomes
By following the troubleshooting steps outlined, customers can expect improved integration functionality between Azure DevOps and Agile Development 2.0, ensuring better data consistency, timely updates, and effective management of work items.
For enhanced visibility, enabling detailed project logging can assist in identifying and resolving integration issues.
Resolve common issues that you might face while working with the integration of Azure DevOps and Agile Development 2.0.
| Issue | Action |
|---|---|
|
The export action is not working. |
|
| Sprint is not imported from Azure DevOps to Agile Development 2.0. | Sprints are not imported to Agile Development 2.0 for one of the following reasons:
|
|
An assignment group is not populated for a story or an epic. |
If the team is not associated with an assignment group in Agile Development 2.0, it can result in assignment group not being populated. Verify that project integration settings exist for your Azure DevOps team. If the area of a work item is mapped to multiple teams, the assignment group for that work item in Agile Development 2.0 is empty. In such cases, you can manually select an assignment group for this work item. |
|
A value from a field in Azure DevOps is not populated in Agile Development 2.0. |
Verify if the custom field map is configured. |
|
The value of Priority or State fields from Azure DevOps is not populated in Agile Development 2.0. |
Verify if the custom state map is configured. |
|
An update by a user in Azure DevOps is not updated in Agile Development 2.0. |
Ensure that the user credentials that are used to set up the integration of Azure DevOps with Agile Development 2.0 are not used to perform record updates. |
|
The work item is deleted in Azure DevOps but not deleted in Agile Development 2.0. |
Ensure that the Can Delete field in the Application access of the respective tables is set to true. For details, see Table design and runtime settings. |
|
Deleting a project, team, or area does not result in any action in Agile Development 2.0. |
After deleting the project, team, or area in Azure DevOps, the Azure DevOps administrator must manually delete the corresponding Azure DevOps project and its associated stories in Agile Development 2.0. |
| New Azure DevOps projects are not imported automatically. | Manually discover projects from the Azure DevOps instance record to immediately synch the project updates or schedule a job to discover and import these updates on a daily basis. For more details on the scheduled jobs, see Schedule jobs to import projects, teams, areas, and work items from Azure DevOps. |
| Imported work items (epics and stories) of a project have no assignment group associated with them. |
Ensure that you have team integration settings for this project. For more information, see Associate Azure DevOps projects with assignment groups in Agile Development 2.0. The assignment group associated to any imported work item of an Azure DevOps project is based on the team integration settings of that project. If the project does not have any team integration setting, the imported work item will have an empty assignment group. |
| Changes made to iterations in Azure DevOps are not reflecting immediately in Agile Development 2.0. | Manually import iterations from the Azure DevOps project record or schedule a job to discover and import these updates daily. For more details on the scheduled jobs, see Schedule jobs to import projects, teams, areas, and work items from Azure DevOps. |
| The UI actions for Connect, Disconnect, and Validate and Fix result in an error when using for the first time. | This error is a known issue. Retry the UI action. |
| When the Description field has & in Azure DevOps, it renders as & in Agile Development 2.0. | The field mapping between Agile Development 2.0 and Azure DevOps is not supported for HTML fields. |
| Export still works when the webhooks are de-registered. | Webhooks are only to import data from Azure DevOps to Agile Development 2.0. To stop the export of workitems, de-select the Export Work Items checkbox for the project. |
Enabling detailed project logs
To view all the details on project logging, enable the integration project logging property. For more information, see Enable detailed project logging in Microsoft Azure DevOps Integration with Agile Development 2.0.