CardBoard Integrates with JIRA

 JIRA trailer

Connect to a JIRA project 

 Staying connected to JIRA

Visualizing JIRA in CardBoard

Configuring JIRA correctly


Confluence and Jira

Now you can embed your User Story Maps in Confluence

Confluence is a good tool for those who need to documentation in their software development process. After you build your story maps simply put them into Confluence so everyone on the team can stay up to date. If you update your story maps in CardBoard, the map will also be updated in Confluence.

Check out the CardBoard AddOn for Confluence in the Atlassian Marketplace

Integration Features

  • easy-copy
  • Simple

    Integrating with JIRA 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!

  • bidir
  • Bi-Directional

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

  • vis
  • 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.

  • hie
  • Hierarchical

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


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

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

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.