CardBoard Integrates with Azure DevOps and on-prem TFS

The integration

How to connect your board to Azure DevOps

Agile Template Hierarchy

When using the Agile template, Feature work items are placed in the first row. User Stories are placed in other rows. User Stories that are children of a Feature are placed underneath the Feature in order for you to see the relationship.

Scrum Template Hierarchy

When using the Scrum template, Feature work items are placed in the first row. Product Backlog Items (PBI) are placed in other rows. PBIs that are children of a Feature are placed underneath the Feature in order for you to see the relationship.

Logging into Azure DevOps

If you have issues logging into Azure DevOps, try using Personal Access Tokens (PAT) instead. Check out this article on using Personal Access Tokens to authenticate from Microsoft.

If you want to log in using your username and password credentials, you need to make sure you enable alternate credentials. To do this, first click your profile picture in the user right hand corner. Next, click on Security. Then click on Alternate credentials in the navigation menu. Select Enable alternate authentication credentials and finally click on Save.

simple trello

Simple


Integrating with Azure Dev Ops is as easy as pressing a button! Authorize a connection between Azure Dev Ops and CardBoard, select a board to sync. We’ll take care of the rest.

tied trello

Tied


Our integration Azure Dev Ops is tied so that changes in each application reconnect every time between the story map and project.

bi-directional trello

Bi-Directional


Integrations are true syncs. Changes or additions made in Azure Dev Ops will be reflected in CardBoard, and vice-versa.

trello vision

Vision


Remove the project’s backlog of lists, and replace it story maps that make sense and contextualizes stories.

Hierarchical


On the initial sync, CardBoard will take the cards on the uppermost row and create them as Features in Azure DevOps. All the cards below and to the right (until another ‘Feature’ card) will be created as stories of that Feature in Azure DevOps.