Linking new features to user stories

We currently use Greenhopper for JIRA, and I would like to attach new features to a particular user story. So the workflow would be something like:

Open a user story - The user would like to do XXX because ...

This story consists of new features. I open the features and would like to make them children of the story.

I can create a custom linking relationship, "belongs to", but it seems like this would be a standard behavior. Is there a way to do this in greenhopper/JIRA?

I know that for Epics I can link a story to an Epic, but I don't know how to (other than I described with a custom linking) link a feature to a story.

I want to avoid using subtasks for stories because sometimes the features have subtasks, so I want to be able to add subtasks for specific features.

2 answers

1 accepted

Accepted Answer
1 vote

I know that for Epics I can link a story to an Epic, but I don't know how to (other than I described with a custom linking) link a feature to a story.

Why are you worried about using standard links if they provide the required functionality? Greenhopper is ready to deal with standard links, in fact that is the way that the Rapird Board expects users link stories to other issues (see the attached picture). If you don't use standard links, then you will "break" such feature.

It's not that I have a problem with standard links, but I don't like using "relates to" for linking an epic to a story. I'd like to show more of a hierarchy that a story is part of an epic.

The Links Hierarchy Structure plug-in (developed by me) builds such Epic hierarchy (see the attached picture).

Regarding the "relates to" link type, you can use your own customized links like "belongs to". That will work with JIRA/GreenHoper/Rapid Board as well as with the Hierachy plug-in.

Hope it helps.

Pablo

Thanks, I wasn't familiar with the links hierarhcy plugin.

I would suggest that a new feature is broken down into epics rather than a story consisting of features. Stories need to have sub-tasks, these can' be avoided in best practice.

Like you say epics have multiple stories within them. Epics in GreenHopper 6 are still a lab feature and need to be enabled.

There is also a linking solution outlined here.

I don't think epics are necessary for every story though. But I'll check out the new features in greenhopper 6.

No epics not necessary for every story but every story should have (sub) tasks, that's best practice anyhow...

Thanks, appreciate the update.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 25, 2018 in Jira

Atlassian Research Workshop opportunity on Sep. 28th in Austin, TX

We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...

449 views 7 5
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you