The work item stays in Azure DevOps

The work item stays the work item

There are two different connections. After you start a trial, connect Azure DevOps from Account → Integrations so work items can be pulled and written back. That is not the Boards extension bind. IbisFlow does not become a second backlog. This page does not bind the organization or start a PAT flow.

1. A thin work item will hurt in refinement

   If the item is still a title and a hope, the room will invent the work. Shape it first so ranking and sizing have something real to talk about.

2. Shape it while it is still that work item

   You add the questions and the product context on the connected work item. You save back to the same item — not a copy that only lives in IbisFlow. The Boards extension does not import this work item. You connect it from Account → Integrations after you start a trial.

3. Rank it when more than one voice needs a say

   Stakeholders can score that same work item. When you publish, the ranking writes back. The slide deck is not the system of record.

4. Size it with the room, then write the number back

   The team votes on the same work item. An accepted estimate writes back to Azure DevOps. The item you sized is the item the team will build.

Visual Studio Marketplace

The extension listing is Free. IbisFlow itself is a separate trial or plan. If you opened this from Boards, go back to the extension to connect the organization.