The story map provides a visual design of the product backlog and it enables a rich in detail overview of the entire product ensuring transparency and shared understanding among stakeholders. This includes defining user personas, custom card templates, custom card annotations, releases with a dedicated release view and reports (status and estimation reports are available). The Search & filter function enables endless options to find and highlight critical information over a discussion e.g. displaying a specific user persona’s journey.
​
We advise to plan your product in StoriesOnBoard. Over a story mapping workshop collect the main goals and steps your users will take and collect user stories and organize them into releases. Once you have the desired content in depth, push cards or entire releases to GitHub. Once a card is connected to GitHub, all changes e.g. card title, description and status will be synced.

The story map offers a great overview and additional possibilities to drive product management activities. Access the big picture and take advantage of many customization options to plan and deliver great products that people will love to use.

As both GitHub and StoriesOnBoard use Markdown for the description, they will be appearing the same at both places.

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.

💡 Tip - Learn more about How custom workflows work on StoriesOnBoard.

Let’s see an example where status mapping is in operation. Additionally, there is a label for exported issues with the value of “StoriesOnBoard” to indicate in GitHub when an issue originates from StoriesOnBoard.
​
If an issue’s status is changing in GitHub and the card is already in sync with StoriesOnBoard, then the status will be updated on the story map according to the label you apply.
​
​

Releases are synced automatically with milestones only from StoriesOnBoard to GitHub. If needed you can import them manually from the other way around as well.
​
Milestones will be created when a card is pushed with a release not existing in GitHub yet. Their names are synced when they are changed in StoriesOnBoard.

Learn more about: