Integrating a story map with a GitHub repository allows teams to plan more effectively, utilizing the visual power of story mapping to achieve transparency and shared understanding among stakeholders. Bring the team around to the story map to see the big picture and take advantage of real-time and bidirectional sync with GitHub to keep everyone up to date at all time.
​
The integration makes it possible to plan releases on the story map and push cards to GitHub for execution. With the powerful integration between StoriesOnBoard and GitHub you can facilitate product discovery, define user journeys, put user stories into context and schedule releases to build and manage amazing products from the very beginning. This allows to do product discovery with user centric approach to build great products that users love.

To be able to setup any integration with a story map you need to have an Admin user role on StoriesOnBoard. Additionally, you also need to hold Admin rights on GitHub as well to be able to make the necessary changes.

Open the story map you want to connect to aGitHub repository and open “Settings“ and select “Integration settings”.

Enter your GitHub Personal access token. Then click to “Connect”.
​
💡 Tip - Learn more about How to generate your Personal access token on GitHub.
​

Select a GitHub repository you wish to connect your story map with. Then click “Connect repository”.

Setup what would you like to keep in sync between StoriesOnBoard and GitHub:

You can setup a label that can appear in GitHub when you push issues from StoriesOnBoard to GitHub.

During import you can enable or disable the following import settings:

To make sure user stories’ statuses are going to be synchronzied, setup status mapping between StoriesOnBoard and GitHub. Link GitHub labels with StoriesOnBoard statuses.

Once you successfully connected to your Trello instance, you will be able to access Integration Settings for Trello as following:

Cards from StoriesOnBoard will be synchronized with GitHub in real-time and bidirectional if you enable the following options:

There is a possibility to distinguish those cards that were created in StoriesOnBoard when you export them to GitHub. This allows you to have a solid understanding about each newly scheduled issues coming from StoriesOnBoard helping the team who works in GitHub.
​

During import you can enable or disable the following import settings:

When you link a story map to your GitHub repository, it is important to be clear about what is happening with your issues on both StoriesOnBoard and GitHub. By default GitHub offers only two statuses for issue management. An issue can be either Open or Closed.
​
Status mapping makes it possible to enhance your workflow and deliver more information for team members by using GitHub labels to indicate additional statuses for your issues. If you are using labels in GitHub to better differentiate statuses, you can map them to statuses in StoriesOnBoard by using the label specifiers:
​
💡 Tip - Learn more about How custom workflows work on StoriesOnBoard.
​