CardBoard Integrations FAQ


With the new release of improved CardBoard integrations, we thought there might be some questions around what it does, what it can do, and best practices, so we created this page to address those and many more! Welcome to the CardBoard Integrations FAQ page, where we’re only going to talk integrations.


How do I connect to my tool’s instance?

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.



How do I connect to VersionOne with an access token?

To connect to a CardBoard board to VersionOne project with an access token, you must create an access token from within VersionOne first. Those instructions can be found here.

Once the access token is created, to connect your board to your VersionOne instance all you need is your VersionOne username and access token, and you’ll be able to tie your board with a project.



 What are hierarchies?

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.

With our most recent release, this feature does not work yet in Pivotal or Rally. Coming soon!



How do hierarchies work with JIRA?

On the initial connection to a JIRA project, CardBoard assumes two levels of hierarchy, where the topmost row of cards are epics and the cards below are stories of corresponding epics.



How do hierarchies work with VersionOne?

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.)



Can I sync one board to multiple projects? How about multiple boards to the same project?

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.)



I’m connected to my JIRA project, but I get an error saying I need to enable story sizes in my JIRA project. How can I do that?

For story sizes from CardBoard to be synced into your JIRA project, you must turn on story points as a entry configuration in your project. (They are not turned on in default Scrum software development.) To do so, go to [project administration], select [screens], select the “pen” of your main screen scheme, select the screen scheme’s name, and at the bottom in the [Select Field..] text entry and type “story points” and hit enter. For JIRA’s official documentation, look here.