daniel

← Customer Feedbacks for StoriesOnBoard

My feedback

8 results found

  1. REST-API

    220 votes
    14 comments  ·  General  ·  Admin →
    How important is this to you?
    An error occurred while saving the comment
    daniel commented  · 

    How about instead of a rest api, just broadcast events that we can subscribe to via https://synadia.com/ or nats.io

  2. Synchronize a storymap with multiple Pivotal Tracker projects

    22 votes
    6 comments  ·  General  ·  Admin →
    How important is this to you?
    daniel supported this idea  · 
    An error occurred while saving the comment
    daniel commented  · 

    fyi this idea is very similiar in spirit to the one linked below and could really help SOB with wider adoption especially enterprise clients....

    https://storiesonboard.uservoice.com/forums/276721-general/suggestions/34284526-github-multiple-repos

    An error occurred while saving the comment
    daniel commented  · 

    Tracker Suggestion / Workaround
    In tracker it's possible to push everything to a single Tracker project, then to use the workspace view to drag stories into different Tracker projects. This is really a nice workflow *but* when the story moves projects, the Stories on Board link is broken. It would be wonderful if the link would reflect the correct project. Trackers just uses a simple url for stories in the following format where the story ID is the always unique, even if the project changes. Therefore, if I have the following story
    https://www.pivotaltracker.com/n/projects/2231783/stories/164583925

    Then I move it to another project, it will then have this url
    https://www.pivotaltracker.com/n/projects/1241422/stories/164583925

  3. Syncronize one storymap with multiple issue tracker projects

    17 votes
    5 comments  ·  General  ·  Admin →
    How important is this to you?
    daniel supported this idea  · 
    An error occurred while saving the comment
    daniel commented  · 

    This would be awesome.

    Tracker Suggestion
    In tracker its possible to push everything to Tracker, then to use the multi-project view and to drag Stories on Board stories into different projects. This is really a nice workflow *but* when the story moves projects, the Stories on Board link is broken. It would be wonderful if the link would reflect the correct project. Trackers just uses a simple url for stories in the following format where the story ID is the always unique, even if the project changes. Therefore, if I have the following story
    https://www.pivotaltracker.com/n/projects/2231783/stories/164583925

    Then I move it to another project, it will then have this url
    https://www.pivotaltracker.com/n/projects/1241422/stories/164583925

    For Github it would be amazing to be able to find something similar. One workaround that has been discussed but not tested is to create a separate 'umbrella' project and then use gitsubmodules. This isn't ideal. Maybe a blue activity card could be associated with a specific repo? That might work...

  4. GitHub multiple repos

    9 votes
    4 comments  ·  General  ·  Admin →
    How important is this to you?
    daniel supported this idea  · 
    An error occurred while saving the comment
    daniel commented  · 

    Resurfacing this feature after some years... a quick look at CodeTree explains all of the problems with pushing cards to a single repo. It would be AMAZING to see SOB offer similar support or a clear work also the SOB github integration seem to be 6 years old now and can use some love
    https://storiesonboard.com/blog/github-integration

    Problem with Managing Stories Across Multiple Github Repos
    https://codetree.com/guides/managing-issues-across-multiple-github-repositories

    After a few years without stories on board, I'm about to spearhead a new project that is a distributed system spanning several github repos and I know this is going to come up again with the team...

    Thank you!

    An error occurred while saving the comment
    daniel commented  · 

    this is a major issue. I'd love to hear how this is dealth with

  5. Implement GitLab issue integration

    82 votes
    1 comment  ·  General  ·  Admin →
    How important is this to you?

  6. Export/Print details in PDF format

    8 votes
    2 comments  ·  General  ·  Admin →
    How important is this to you?
    An error occurred while saving the comment
    daniel commented  · 

    Essential and tough to find a good alternative

  7. regex done

    0 votes
    0 comments  ·  General  ·  Admin →
    How important is this to you?
    daniel shared this idea  · 

  8. Sync attachments with JIRA

    56 votes
    6 comments  ·  General  ·  Admin →
    How important is this to you?
    An error occurred while saving the comment
    daniel commented  · 

    I would make this general and support all issue trackers. If i use stories on board, its power is that it can support many issue trackers on the back end

Feedback and Knowledge Base

(thinking…)