Sync structure of themes/epics/stories with JIRA
"Is it possible within the synchronization of JIRA to set some sort of interface structure where for example the epics are parents of user stories and etc.? Just like the setup in JIRA?
For example on the screen you now see a blue card with date of import, and a yellow card with the number of the user stories that are imported. It would be nice as user to have the ability to link the blue one to for example epics and the yellow one to user stories and the white ones to tasks. Is it possible to have such feature added?
Jan-Willem"
AdminArpad Tamas
(co-founder, StoriesOnBoard)
shared this idea
We are happy to inform you that this feature is finished and rolled out recently. Please take a look at our help center article for more information:
Or contact our support team any time.
-
Anonymous
commented
As a < Product Owner >
I want < to see the user story mapping structure preserved >
So that < I don't have to start over again > -
"When I push a release to Jira, is there someway to view the cards with each other, like in a release in Jira or as part of an epic? My context is that I push cards within an iteration of my storymap and then there are some people in my organization that use the story map but some people don't."
- Daniel -
John De Goes
commented
This feature is very important to minimize work. Without this feature, pushing issues to JIRA is just the first step in the process: all the issues have to be edited manually to re-create information in the story map.
Ideally the mapping would be as follows:
Goals (top-level) -> Components
Activities (second-level) -> Epics
Features (third-level) -> Issues
User Stories (fourth-level / subtasks) -> Subtasks
JIRA was not designed for story mapping, but in combination with Agile, I think you can do a pretty good mapping here.
This is the approach taken by FeatureMap, for example, which tries to re-create the hierarchy in JIRA.
-
Vihang
commented
We would like stories on board for all our planning sessions as well as high level story tracking. For this it's important that it can sync 1:1 (Epics and stories) with stories on board
-
Thanks for the reply Jan-Willem!
We discussed and still thinking about that.
Till then please vote for it who would need it.
Thanks!
Arpi -
Jan-Willem
commented
Hi,
Sorry for my vague feature request.
We use JIRA Agile for our user story tracking. These user stories are part of an epic which will be added to a certain sprint. Just pretty straight forward. Our user stories are planned into sprints, after that tasks and sub-tasks are created.Our idea was that it would be nice to have the feature that during the import tool it would be possible to customize the interface between storiesonboard and JIRA. I gave above an example but in case you know a better way.
-
Dear Jan-Willem,
We are thinking about this and gathering information on how people are structuring issues in JIRA.
Would you please help me with a few questions? I may misunderstand some of the notions you used.
Do you use JIRA Agile or standard JIRA?
Do you schedule your tasks or your stories in JIRA? As I understand white cards in StoriesOnBoard that can be scheduled into releases (or spirints) are more straightforward to map to stories in JIRA Agile as they are also scheduled. But it's subtasks aren't scheduled, they are just the implementation breakdown of the stories. Do I understand it right?
Thanks!
Arpi