Custom Workflow

This article will cover the feature set and usage of custom workflow in StoriesOnBoard.

Tamás Párványik avatar
Written by Tamás Párványik
Updated over a week ago


What is custom workflow?

With the help of custom workflow, you can use custom statuses in StoriesOnBoard. It can be really useful, even if you are tracking your team's work in StoriesOnBoard or if you are using other tracking tools, like Jira with lots of status types. Let's see how it works.

Please note, that custom workflow is only available in the standard plan or above.

How can you access it?

There are three ways to access the custom workflow settings. The first one is from the upper right tool menu.

You can also access the settings by clicking on the status of an unlinked card. It is important to mention unliked cards because the status of linked cards is controlled by another tool like Jira so they can't be clicked in StoriesOnBoard.

Workflow settings

Custom workflow settings can also be found in the integration settings, under the status mapping section.

In the settings window, there are three main statuses, To Do, Active, and Done. You can add new statuses under these.

The first status under To Do will be the default for all the new cards created. Hovering on any staus will reveal a few more options which are editing the name, reorder and deleting.

Clicking on the color rectangle next to the name of the statuses will bring up the color selection window which has ten predefined colors.

It is important to mention that if you are about to delete a status that is in use you need to select another status for all of the cards where the deleted status was used.

Creating a copy of the story map will also copy all the status settings, so it is a good way to create a template for future projects for example.

To achieve this, it is also possible to export the story map as xlsx (backlog format) with all the statuses.

And import it back at new story map creation to have the same settings.

💡 Tip

Learn more about Custom Workflow

Did this answer your question?