JIRA Concepts: Difference between revisions
Jump to navigation
Jump to search
(→Issue) |
(→Issue) |
||
| Line 22: | Line 22: | ||
An issue can have [[#Sub-Task|sub-tasks]] that can be assigned and tracked individually. | An issue can have [[#Sub-Task|sub-tasks]] that can be assigned and tracked individually. | ||
Operations: | |||
* [[JIRA Operations#Configure_an_Issue.27s_Fields|Configure an Issue's Fields]] | |||
==Types== | ==Types== | ||
Revision as of 22:33, 27 February 2016
Internal
Project
- Administering a Project https://confluence.atlassian.com/jiracorecloud/administering-a-project-765593096.html
Component
- Organizing work with components https://confluence.atlassian.com/jiracorecloud/organizing-work-with-components-765593655.html
A component is a way to group issues within a project. Components do not have dates assigned to them. They can can have a component lead who could be a subject matter expert.
Issue
- Working with issues https://confluence.atlassian.com/jiracorecloud/working-with-issues-765593800.html
- Creating issues and sub-tasks https://confluence.atlassian.com/jiracorecloud/creating-issues-and-sub-tasks-765593815.html
- Customizing the issues in a project https://confluence.atlassian.com/jiracorecloud/customizing-the-issues-in-a-project-765593617.html
An issue is a unit of work that need to be done. The issue is the building block of any project.
An issue can have sub-tasks that can be assigned and tracked individually.
Operations: