🔁 Sync Suivi with Azure DevOps (work items ↔ board)

Connectors and Integrations
,
1

Vous gérez vos User Stories / Bugs / Tasks dans Azure DevOps et vous voulez les présenter / piloter dans Suivi (Tableau, Kanban, Dashboard
) ?
Le connecteur Azure DevOps permet de synchroniser des work items d’un projet AzDO vers un board Suivi
 et mĂȘme de crĂ©er des work items AzDO depuis Suivi (dans certaines conditions).

:books: Doc pas Ă  pas ici :
https://doc.suivi.work/fr/articles/1763745187-synchroniser-des-donnees-avec-un-board-azure-devops

:white_check_mark: Key takeaways (important rules)

  • Synchronization is bidirectional:
    • AzDO → Suivi: creation + update of elements
    • Suivi → AzDO: creation only (if the work item does not already exist in AzDO)
  • Once a work item is synchronized, it becomes “AzDO property”: synchronized fields are no longer modifiable in Suivi.
  • 1 connection = 1 work item type (but you can create multiple connections on the same board).
  • The Area Path filter is strict (sub-areas are not included if you don’t target them).
  • Only Child relationships are synchronized (list visible in Suivi, not modifiable).

:locked_with_key: Prerequisites

  • An Azure DevOps Personal Access Token (PAT) (max 1 year validity), with appropriate Work Items rights.
  • :warning: Before configuring the connection: your board attributes must already be ready (columns / types).

:rocket: Setup (ultra summary)

  1. Board > 
 > Connectors > New connection > Azure DevOps
  2. Fill in: Name, PAT, Organization
  3. Select: Project + Area Path + Work item type
  4. Associate Suivi fields ↔ AzDO fields (you don’t have to synchronize everything)
  5. Finish, then launch synchronization (from the connection, the board menu, or the sync button)

:counterclockwise_arrows_button: Synchronize (both ways)

  • AzDO → Suivi: launch synchronization and work items appear on your board.
  • Suivi → AzDO: from the Table view, double-click on the Connection attribute cell to synchronize an item (or multiple with Shift + select).

:speech_balloon: Tell us in the comments: what do you want to synchronize first (User Stories, Bugs, Features
) and for what purpose (product management, reporting, backlog preparation
)?

1 Like
Uses azdo connector to follow your features developpment
2

:light_bulb: Similar connector idea: GitHub for reporting:

  • bugs :beetle:;
  • project planning :date:
1 Like
3

Hi David, thanks for the idea :light_bulb: — it’s very relevant (especially for centralizing bugs + planning).

For us to properly process it on the product/roadmap side, could you please repost it in the “Feedback & Ideas” category (ideally 1 idea = 1 topic) and give us a bit more detail on what you expect from a GitHub connector?

A few points that would help us a lot:

  • GitHub Scope: Issues? GitHub Projects (v2)? PRs? Milestones?
  • Sync Direction: GitHub → Tracking only, or also Tracking → GitHub (creation / update / closing)?
  • Expected Mapping: statuses, assignees, labels, priority, dates, sprint, PR/commit links, etc.
  • Update Mode: real-time (webhooks) vs scheduled sync, and approximate volume (number of issues).

With this, we can evaluate the interest, complexity, and see how to integrate it into the roadmap :+1:

1 Like