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?
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot