Add two-way integration for Github Issues
Add integration for Github Issues
It’s available now! You can connect your map to a GitHub repo. More details here: https://storiesonboard.com/blog/post/github-integration---what's-new-in-storiesonboard---october-2016
-
Thanks for the comment Alex!
Github integration in itself won't allow you to sync a map with two issue trackers. That is another task.
Would you mind adding your comment there as well and voting on it? -
Alex Stanciu commented
My ideal workflow:
People submit issues to Github. SOB retrieves the issues, I can priorities, map, put cards into releases. Then I can push a release to an issue tracker (Pivotal) where our engineering team works on them. Once done, status is pushed back to SOB, and (super wishful thinking here) SOB closes the issue in Github when done.If the planned Github integration will allow for this type of workflow... oh man :)
-
Thanks Bret for the details!
Currently we are thinking in something like this: https://drive.google.com/file/d/0B3RoLsiZFUwJdjJYdENRMko3UFE/view?usp=sharing -
Bret Mogilefsky - XFB commented
For reference, here's how aha.io can be configured to map releases, features, and requirements (aka stories) and status to GitHub.
http://support.aha.io/hc/en-us/articles/202001027-Integrate-with-GitHub-IssuesWe'll be configuring aha.io to map features and requirements both to GitHub issues. We'll probably make a column in SOB for "Features in this Release" and put the cards resulting from the extra feature-level issues in GitHub there.
-
Bret Mogilefsky - XFB commented
We are so glad to see that work has started on this!
Please keep the tag mapping configurable... We use other tools like waffle.io and aha.io that will also use tags on GitHub issues to map status, and it would be great to be able to make them represent the same values in the different tools.
-
"In any case, two-way push from StoriesOnBoard to Github Issues would be nice, assuming the appropriate mapping:
SOB Release -> Github Milestone
SOB Status -> Github Status + Tag (Github Status only has open / closed, so tags are needed for Ready / Doing).
SOB Description - > Github Description
SOB Attachment -> Github Attachment
SOB Priority -> Github Tag (Github Issues has no way to represent priority)
SOB Estimation -> Github Tag or metadata in Github Issue (e.g. Estimation: 12 hours at the top of ticket)." - John -
Sarah Allen commented
I use Waffle.io on all of my projects because of its github integration. I would LOVE to do story mapping on all of my projects if I could find a tool that does that with github issues integration. Could that be storiesonboard?
-
Bret Mogilefsky commented
This would be amazing... If StoriesOnBoard did the same thing with GitHub as it does with Trello, Jira, etc, then between SOB, GitHub, and WaffleIO/ZenHub, an enormous amount of status-tracking would be eliminated!