Jira Premium and Enterprise customers can also create additional levels in their issue type hierarchy. The issue type hierarchy settings allow you to manage the default hierarchy levels for issue types in Jira. Subtasks can be described and estimated separately to their related standard issue and can help your team better understand and estimate similar work in the future. This can be helpful if your team has a task that requires multiple people working on it, or if your team underestimates the scope or complexity of their work. Subtask issues, which can help your team break a standard issue into smaller chunks. For business teams, standard issues represent and track your team member's daily tasks. For service teams, standard issues represent different requests made by your team's customers, like requesting service or support, or reporting problems or incidents with your infrastructure.
#Jira task board software
For software teams, standard issues (like bugs or stories) estimate and track the effort required to build an interaction or other end goal in your team's software. In Jira, standard issues are where daily work is discussed and carried out by team members. Standard issues represent regular business tasks. For business teams, epics may represent major deliverables or phases of a project. For IT service teams, epics may represent a major service change or upgrade. For software teams, an epic may represent a new feature they're developing. What are issue type hierarchy levels?īy default, Jira supports three levels of hierarchy:Įpic issues, which represent high-level initiatives or bigger pieces of work in Jira. Learn more about structuring work for your agile team. Or if a task has too many subtasks, it might deserve to be split into multiple tasks.
For example, if an epic has too many stories, it might be a sign that your epic can be split into multiple epics.
#Jira task board pro
Pro tip: To reduce your number of child issues, try splitting the parent issue. If you use time tracking, you won’t be able to include subtasks. Instead of viewing your child issues from the issue view, you’ll have to view them in search - which you can go to straight from the issue view. Since the issue view can only display up to 500 child issues, we recommend limiting your issues to that amount. Rather, any issue type can be both a parent and a child issue - the only exception being subtasks, which can only be a child since there aren’t any issue types below it in the hierarchy.įor example, if you have this issue hierarchy:Īs a parent issue, an epic can have stories, tasks, and bugs as child issues.Īs a parent issue, a task can have subtasks as child issues. This means that the parent and child relationship isn’t limited to specific issue types. a story that’s made up of subtasks.Ī child issue is an issue that sits below another issue e.g. Parent and child are terms that describe a type of relationship between issues:Ī parent issue is an issue that sits above another issue e.g. Get started with these default issue types or create your own. We provide suggested issue types to help you classify tasks to work in common agile software development or IT service management methods.
Multiple issue types help you search and sort the work your team takes on, track the progress of specific types of work, even estimate how well your team responds to bugs or how fast they complete larger initiatives.Įach Jira product comes with default issue types to suit the needs of your projects and teams. You can customize your issue types to match any method of project management you want. They can help your team build more structure into your working process.
On the board or backlog, select an issue.Įnter a description for the subtask and select Create.Issue types distinguish different types of work in unique ways, and help you identify, categorize, and report on your team’s work across your Jira site. Note that you cannot create subtasks under epics or other subtasks. You can create subtasks under any standard issues, like stories, bugs, or tasks. Navigate to your team-managed software project. If your project doesn’t have the subtask issue type, you’ll need to add it: By default, team-managed projects have subtask issue types enabled. Subtask issue types are different from regular issue types. This allows you to break down the work in your project to smaller, more manageable pieces. In Jira, an issue can have subtasks that can be assigned and tracked individually. Learn more about the difference between company-managed and team-managed projects. If the lower-left of your project sidebar says you're in a company-managed project, check out these company-managed project articles instead.
0 kommentar(er)
