CardBoard Integrates with VersionOne

The integration

How to connect your board to VersionOne

Integration Features

Simple

Integrating with VersionOne couldn’t be easier. Simply enter your instance’s URL, your username and password, and which project you’d like to integrate with, and hit sync!

Tied

Our integration is tied, meaning you don’t have to reconnect every time you want to sync between your story map and project.

Bi-Directional

Your sync will be a true sync, meaning changes or additions made in VersionOne will be reflected in CardBoard, and vice-versa.

Visualize

Take your project’s backlog out of lists of to-dos and turn it into a story map that makes sense and contextualizes your stories.

Hierarchical

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

FAQ:

To connect a CardBoard board with a Project Management System (e.g. JIRA, VersionOne, Pivotal, Rally) project, the CardBoard user is required to have read/write permissions within the V1 project. This means that anyone who can edit the project can connect the project to a board in CardBoard. You can create the connection with you instance’s unique URL (in the case of Pivotal or Rally, the unique URL is not needed, unless you’re hosting it). Once that connection is made, it stays until it is disconnected from CardBoard.

The new release of CardBoard now differentiates between epics and stories when syncing with tools. When you toggle on and off the hierarchy button we show two colors – one representing epics the other stories. When a sync is made those cards will now create corresponding epics or stories in your tool, with your epics’ stories correctly positioned. (With this release, hierarchies are only ‘calculated’ in CardBoard when the board is first connected to the tool, i.e. subsequent stories created in CardBoard will be synced into your tool as a story without an epic, even if the story aligns with the other epics.)

On import of a tool’s stories to CardBoard, CardBoard will place epics on the top row and corresponding stories directly below.

On the initial connection with a VersionOne project, CardBoard assumes three levels of hierarchy. Thusly, the topmost row are epics, the second row are child epics of correspondingly above epics, and everything else is stories of the epics of above. (For a good example of what a map like this would look like see Flights Done Right.)

As of now, you can only sync one CardBoard board to one project (at a time) and everything is transferred — there is no selective sync. That is, if you make a change in CardBoard that change will be synced to your project. Same for the other way around, when you make a change in a project and sync with CardBoard, your board will reflect that change. Unlike blackholes, all information is retained and transferred.

You can, however, connect multiple boards to a single project where all those boards will contain the same data as the other boards and the project. (We recommend this only with a very intentional meaning behind doing so.)