Dear Arpad,
Thank you for this awesome release planning tool. It is by far the best story mapping tool I've used and your support for jira, tracker, and trello is spot on.
In tracker, an epic is just a special designated label.
I'd be happy to show my team's "epic" workflow in tracker. In general an epic is an end to end release and maps directly to a SOB release. Though I have worked with teams using epics to group stories related to a specific component (e.g. database adapter, photo upload), I believe this is less conventional.
Without this feature. I typically push stories in SOB to tracker. Then I navigate to tracker, locate the new stories, select them stories, and lastly I add to the tracker epic.
Daniel
Dear Arpad,
Thank you for this awesome release planning tool. It is by far the best story mapping tool I've used and your support for jira, tracker, and trello is spot on.
In tracker, an epic is just a special designated label.
I'd be happy to show my team's "epic" workflow in tracker. In general an epic is an end to end release and maps directly to a SOB release. Though I have worked with teams using epics to group stories related to a specific component (e.g. database adapter, photo upload), I believe this is less conventional.
Without this feature. I typically push stories in SOB to tracker. Then I navigate to tracker, locate the new stories, select them stories, and lastly I add to the tracker epic.