Skip to content

General

346 results found

  1. 10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Include story card URL/link in backlog xls export

    When using the export to xls function, we often want to pop back and forth from the story in the xls and the SOB story, so having the card URL in the row for that card would improve our productivity

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Sync card annotations to external systems

    Card Annotations should sync with Github tags, Jira labels, etc.

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. assign card colors automatically to Jira states

    it would be very nice if the color of the cards is automatically mapped to the state of the card in jira.

    for example:
    * story is in a sprint
    * the story is done
    * story is on going
    * ...

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Tempo Plugin

    Tempo plugin support for StoriesOnBoard

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Support Area paths in Azure Devops / TFS

    Supporting Area paths in the DevOps integration would allow anyone to keep story work items in the proper team and or product.

    Currently you can filter what syncs using a query, but new items go to the default area path.

    If new work items could go to an area path (specified in the story settings) it would keep them in the correct Team/Product.

    28 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Alow create map with multiple projects

    for release managers is important to have all release version in different projects on one map

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. 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…

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

General

Categories

Feedback and Knowledge Base