Jira Agile issue types

JIRA Issue Types

There are generally 5 Jira issue types the 5th one is Sub-task,  can only created from within a Story.

    Epic

• An Epic is used when a feature is large in scale, may take several sprints to complete, and/or may spans multiple components.
• The Epic itself is an umbrella issue. An Epic is comprised of one or more stories.
• Usage: Anyone can create an Epic and put it in the backlog for a project.

    Story

•  A Story or user story is a piece of work that can be completed within a sprint.  It is usually part of an Epic.
• Usage: Anyone can create a Story and put it the backlog for a project.

    Bug

• A Bug is a defect, an error, or a flaw that requires a fix, it can be a code change, a documentation update, configuration change, etc…
• Usage: Anyone can create a bug and assign to himself or someone else or leave it unassigned if they wish someone else to pick it up and work on it

    Task

• Task can be used to breakdown a story into smaller work units that can be completed in a day or two; however, for deconstruction of a story, it is recommended that a Sub-task be used. Using a Sub-task will save the user Jira steps and will be automatically linked to the story since it's created from within the story.

 See Sub-task below.

Tasks can be used to track discrete activities that must be done and may not necessarily be related to a story (for example, fix a Jenkins job); however, if a user chooses to use Task issue type to track work associated with a story, be sure to link the Task to the Story via the Linked Issues and Issue fields as illustrated below.
     
Usage: Anyone can create a task and assign to himself or someone else

 Sub-task

• Sub-task is used to breakdown a story into smaller work units that can be completed in a day or two. Breaking a story down into discrete work units that can be burned down daily will communicate progress on the story.
• Sub-tasks are created from within the story via the More menu option by selecting Create sub-task