Troubleshooting issues for Azure DevOps integration with Agile Development

  • Release version: Washingtondc
  • Updated August 1, 2024
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Troubleshooting issues for Azure DevOps integration with Agile Development

    This guide addresses common issues encountered when integrating Azure DevOps with Agile Development 2.0. It offers actionable steps to resolve integration challenges, ensuring smooth operation and synchronization between the two platforms.

    Show full answer Show less

    Key Issues and Actions

    • Export Action Not Working: Check your custom map configuration and ensure the Enable Export checkbox is selected for the project. Verify that your Azure DevOps password is active.
    • Sprints Not Imported: Sprints in Agile Development 2.0 are created only when a work item is first added to a new iteration in Azure DevOps. To maintain consistency, create sprints directly in Agile Development 2.0.
    • Assignment Group Not Populated: Ensure the project integration settings are correct and that the work item area is not mapped to multiple teams. Manually select an assignment group if needed.
    • Field Values Not Populated: Verify the configuration of custom field maps for Priority or State fields to ensure values are transferred from Azure DevOps.
    • User Updates Not Reflected: Ensure that the credentials used for integration setup are not employed for record updates in Azure DevOps.
    • Deleted Work Items: Set the Can Delete field to true in Application access for respective tables to allow deletion in Agile Development 2.0.
    • Project Synchronization: New projects in Azure DevOps require manual discovery to sync updates. Schedule jobs for daily imports to automate this process.
    • Empty Assignment Groups: Verify team integration settings for imported work items to ensure assignment groups are populated.
    • Iteration Updates: Manually import iterations or schedule daily jobs to reflect changes made in Azure DevOps.
    • UI Action Errors: Known issue; retry the Connect, Disconnect, and Validate actions if errors occur.
    • HTML Field Mapping: Description fields with '&' in Azure DevOps will appear as '&' in Agile Development 2.0 due to unsupported HTML field mapping.
    • Export and Webhooks: Export functionality remains intact even when webhooks are de-registered. To stop exporting work items, de-select the Export Work Items checkbox.

    Next Steps

    For enhanced troubleshooting, enable detailed project logging to track integration issues effectively. Refer to the documentation for information on enabling project logging in Microsoft Azure DevOps Integration with Agile Development 2.0.

    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.
    • Review your custom map configuration.

      If your custom map configuration is invalid or if the required fields are not mapped for that work item, export does not work.

    • Ensure that the Enable Export check box is selected for the project.
    • Check to see if your Azure DevOps password has expired.
    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:

    • Any new iterations created in Azure DevOps do not create a corresponding sprint record in Agile Development 2.0 immediately.

      When a work item is added for the first time to the new iteration in Azure DevOps, only then a corresponding sprint record is created in Agile Development 2.0.

      To ensure consistent data across the two applications at all times, create sprints in Agile Development 2.0.

    • Ensure that there are no overlapping sprints.

    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.