JIRA:Epics，Label和Components [英] JIRA: Epics vs Labels vs Components
问题描述
此博客在JIRA中定义了史诗:
史诗是相当大的工作领域.史诗是功能级的作品，包含许多用户故事.使用上面的示例，史诗可能是整个帐户管理功能以及查看以前购买商品的能力.
因此，如果(作为产品所有者)我要交付一项大型功能，该功能包含许多较小的任务并可能跨越短距离冲刺，那么史诗片是个不错的选择.
但是，我可以轻松地(使用博客中的示例)创建帐户管理"组件，并且与该功能相关的所有任务都将分配该组件.
同样，我也可以轻松地使用"Account_Management"标签，并且作为帐户管理"功能一部分的任何故事/票证都将简单地用该标签进行标记.
所以我的问题是:为什么/在什么情况下使用史诗?为什么/在什么情况下使用组件?为什么/在什么情况下使用标签?即，这三个(主题，标签，组件)似乎都具有非常相似的目的(将一系列问题归为一组)，有什么区别?
对于标签和组件，如果要选择一组，则需要使用问题搜索.如果您使用的是史诗，则也可以使用问题搜索，但是您还可以在JIRA Agile中获得内置功能.</p>
在JIRA Agile板的积压视图中，您有一个Epic选项卡.此选项卡使您可以选择与各个史诗相关的问题.此外，它还具有使向史诗中添加新刊物的功能变得简单.最终的优势是，史诗名称在列表中的问题旁边显示为鲜艳的颜色.当查看待办事项并了解接下来的工作时，这将非常有用.
您可以在Atlassian的使用史诗页面上了解有关史诗的更多信息.
>组件对于技术团队来说非常有用，因为它们可以跨越许多史诗.典型的组件可能是数据库"或"UI". JIRA提供了将特定组件的工作分配给特定JIRA用户的选项.例如，使用数据库"组件创建的所有问题都可以分配给Jill Smith.
标签适应性强得多，并且具有允许多次分配的优点(因此，一个问题可以关联多个标签).标签的使用完全取决于您的使用方式.
This blog has a definition of epics in JIRA:
Epics are significantly larger bodies of work. Epics are feature-level work that encompasses many user stories. Using the above example, an epic might be the entire account management feature and the ability to see previous purchases.
So if (as a product owner) I have a large feature I want delivered that will comprise many smaller tasks and likely span sprints, then an epic is a good choice.
However, I could just as easily create a (using the example from the blog) "Account Management" component, and any task related to that feature have that component assigned.
Similarly I could also just as easily use a label of "Account_Management", and any stories/tickets that are a part of the Account Management feature simply get tagged with that label.
So my question: why/what circumstances would you use an epic? why/what circumstances would you use a component? Why/what circumstances would you use a label? Ie - all three (epics, labels, components) seem to serve very similar purposes (grouping a collection of issues), what's the difference?
With labels and components if you want to select a group of them you need to use issue search. If you are using epics you can use issue search as well, but you also get built-in functionality in JIRA Agile.
In the backlog view of a JIRA Agile board you have an Epic tab. This tab allows you to select the issues associated with individual epics. Plus it has functionality that makes it simple to add new issues to an epic. The final advantage is that the epic name is displayed brightly coloured alongside the issues in the list. This can be very useful when viewing the backlog and getting a feel for what work is coming up next.
You can see more about epics on the Atlassian Working with Epics page.
Components are useful for the technical team as they can span across many epics. A typical component might be 'database' or 'UI'. JIRA offers the option to assign work for a particular component to a particular JIRA user. For example, all issues created with a component of 'database' could be assigned to Jill Smith.
Labels are much more adaptable and they have the advantage of allowing multiple assignments (so more than one label can be associated with an issue). With labels it is very much up to you how you use them.
这篇关于JIRA:Epics，Label和Components的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
