General
346 results found
-
Synchronize statuses from JIRA to SoB without mapping
It would be great if the status of a epic / story is synced to Stories on Board. Now you have to map them to a limited list of features and loose some granularity on the status of an issue.
3 votes -
Story map visibility settings on a workspace level
It would be nice to have an option to disable the visibility of all story maps e.g "Workspace visible" for the entire Workspace, so users can't set this option by mistake.
4 votes -
Sync card colors with labels in Trello
In Jira integration, you can use color names from SoB as labels in Jira. It would be great to have a similar thing in Trello integration. Even better, SoB could sync labels to similar colored ones in Trello.
1 vote -
search filter unscheduled
Allow filtering to unscheduled issues only. There is a release filter but it doesn't have "unscheduled" as an option.
0 votes -
Mattermost Chat Integration
Mattermost is the new slack, but you host your own chat compared to Slack which holds all the chats.
3 votes -
Discussion mode for the map
Allow the map to be put in a discussion mode in a per user manner. In this mode, think about how people in a conference room can stand up and point at cards while they are talking.. So if a user puts the map in discussion mode, then when they click on cards, the card is highlighted in a toggle fashion and that highlight shows up on the browsers of everyone else logged into the map. So on a conference call, the people can follow along with what the presenter is "pointing at".
3 votes -
Allow cards to be in draft mode : Think-Write-Tell-Place
When conducting a meeting that is geographically distributed, people come up with ideas while others are talking. So in the "Think-Write-Tell-Place" methodology, it would be great to be able to "write" while someone else is talking, but not have it show up for other people until it's your turn to talk. Then, taking it out of draft mode will allow it to show up on the board when you get the opportunity to talk about it.
3 votes -
Keep {variable} labels (from board settings) in sync with JIRA
You understandibly only sync (a maximum of) 2 levels to JIRA: either 1st and 3rd or 2nd and 3rd.
I can use the variables on map-level to sync the missing level: fill JIRA label with {activity} or {task} (depending on the 1st setting).
However, they are only sent to JIRA once, on initial push.
When you later either...
a) move the card in storiesonboard, so that it falls under a different parent
or
b) change the name of the labelized card (activity or task) in storiesonboard
... this is not reflected in JIRA.
I can imagine you would not want…5 votes -
Add an OCR import feature for hand written post it notes
Story mapping a large program with dependencies between and deliverables from multi-disciplinary teams usually flows quicker when working with post it notes on large walls. Transitioning to a digital format after the fact can be quite tedious.
1 vote -
Display relevant aggregated work time when filtering
After filtering (by colors, annotations, etc.) it will be great if one can see the aggregated work based on the filtered items.
Usecase: I have 2 teams work on the same project.
I have color coding or annotations to associate cards with the teams.
Now I'd like to see the amount of work each team has by filtering by its color coding.3 votes -
Sync attachments with Azure Devops
Sync attachments with Azure DevOps
22 votes -
Tempo Plugin
Tempo plugin support for StoriesOnBoard
1 vote -
Map to iterations paths within Azure Devops
When syncing from a new board to DevOps for the first time, new iterations are being created regardless if they already exist.As such, it would be beneficial to map releases from Stories On Board to pre-existing iterations in DevOps to avoid
For example, if there is an iteration in DevOps with the same name as a release in SoB, lets say "Release 1", when syncing it will create a new iteration in DevOps called "Release 1 - 1". Then you have to move items from this new iteration to the correct one and delete the newly created iteration.
I appreciate…
3 votes -
WYSIWYG Editor
Why do we have to remember markup options when every descriptor form box currently on the web integrates a WYSIWYG editor (like TinyMCE) into the field, so it is much easier to format and style the copy you are entering.
4 votes -
Re-use Persona's across Boards
Is there a way to share Personas across multiple boards? Working on a bigger system, multiple story maps will have the same person's.
Currently they need to be duplicated for every board manually.42 votes -
Assignment options when pushing to DevOps
Something that would be great is if I could make DevOps specific assignments when I push to DevOps. A few fields that come to mind are Tag, Iteration Path, State, and Assigned To.
I'm using an advanced filter that includes a tag and find myself bouncing back and forth to keep the two synced up.
7 votes -
Allow collaborators to upvote cards
A key element of story mapping is collaborative prioritization/prevalence. IE, understanding how popular a given card might be amongst the participants.
In an in-person setting, this is achieved either by asking participants to spend several minutes writing ideas on sticky notes, then consolidating similar ideas, or asking participants to "dot-vote" on ideas that resonate.
If Stories on Board allowed for live up-voting of cards as they are added, this would come close to replicating the in-person story mapping experience. Collaborators should have a simple mechanism to upvote a card (and ideally could add clarifying comments that would be visible on…
3 votes -
Make a card be reusable when it applies to more than one idea
Sometimes I have the same step that will happen in different user goals. Like "Submit user information"
This is a step in the flow of an admin creating a user and a user registering but the steps are different but the page displayed will be the same, it would be nice to not have two different cards and have one card that is like a function in programming that I can reuse in different places thus not have 2 different issues in JIRA for the same thing
3 votes -
Alow create map with multiple projects
for release managers is important to have all release version in different projects on one map
3 votes -
1 vote
- Don't see your idea?