Synchronize a storymap with multiple Pivotal Tracker projects
Multiple teams can work on the same storymap synced with their Pivotal Tracker projects.
AdminArpad Tamas
(co-founder, StoriesOnBoard)
shared this idea
-
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....
-
David Pattie
commented
This is a blocker for our adoption, we can't move the teams to use the same pivotal project and portfolio team need an overview to pull infra and app development streams together in Stories on board
-
Stewart
commented
This is a key feature for portfolio / product managers, whose work span multiple projects: Be able to see multiple pivotal tracker projects, be able to name (or alias) the project that each epic belongs to, and pick a number of key strategic epics from each project that they want to track (for example: Only track and roll up Epic A, D and E into SOB), and all epics that were chosen are then rolled up directly into one high level SOB Board (working independently of the Tracker workspace feature) - and most importantly - see the updates on each epic when done. This should broaden the product's market appeal, and help all of those who manage multiple related projects.
-
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/164583925Then I move it to another project, it will then have this url
https://www.pivotaltracker.com/n/projects/1241422/stories/164583925 -
Anonymous
commented
Stories on board is great. I would love to use it, but like Arpad, my product has multiple teams working on multiple Pivotal projects. Until your tools supports that, I can't use it.
-
diego.cadenas
commented
A roadmap usually spans multiple teams that do not necessarily share the same pivotal project. This request is to allow to select more than 1 project where cards can be synced back and forth from