I've been going through the documentation on components, and it seems that GreenHopper is shying away from components to focus on epics. Am I right in saying that?
It's true that both components and epics are ways to relate stories. A component was always meant to provide a way to provide structure below the level of a project. If you create a bug, its useful to know that it's related to the Confluence Editor, for example. Components tend to have long lifespans. Epics are meant to provide structure within the story development hierarchy, and as a way to help think about big stories that devolve into smaller stories. Epics can be completed, components typically don't. The epic reporting we are developing reflects this as well.
We use components to relate stories and bugs concerned with functional areas of the product, and epics to talk about feature work. Make sense?
...It's true that there are projects in Jira; but they are merely a way to cut off issues, to tell them apart from other sections of work and to apply rules that are specific to that team (the schemes)....
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!
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