Product teams need all product data organized and structured in one source of truth. For this purpose, we improved and customized our Azure DevOps (ADO) integration. First, our enhanced ADO integration now provides seamless, two-way synchronization for all dependency types:

Once your integration is configured, dependencies automatically synchronize between Craft.io and ADO, offering continuous visibility and effortless updates across both platforms.

Second, to ensure your ADO backlog is well arranged from the moment of sync, users are now able to define default ADO areas for each ADO project. Previously, items synced from Craft.io to ADO would land in generic default areas, forcing users to manually reorder them. This new feature solves that by allowing you to define a specific default ADO area path for each project's newly synced work items. To use it, simply navigate to your ADO integration settings and select “Field & type mapping". There, you can enable the Area field and select your desired Default Area.

Third, to arrange better parentless items synced from ADO to Craft.io, we now allow customizing the name of the default parent items. Craft.io has a robust hierarchy, where each work item has a parent item. Therefore, all parentless items that were synced to Craft.io, were placed under default parent items (Product, Epic, Story) with generic names. But from now on, you can customize the default parents' names and location across syncs. Select for each project the desired default parent name from your existing work items. Then, on the next sync, new parentless items will be synced to it and added as part of its related product hierarchy. To rename your project’s default parent items, you can access this feature in your project's 3-dot menu under "Rename Default Parents".