But there can be many issue types in the Story and Sub-task layers. By default, Jira creates issue types called Story and Task in the "Story" layer, along with several others. And by default, "sub task" and "technical task" are added in the sub-task layer. But an admin can add, remove or rename them.
Issue Types are used to categorize issues depending on their nature. JIRA has some defaults set to help you get started: Bug, Improvement, New Feature, Task, and Custom Issue. Since needs vary, JIRA allows you to add, edit, and delete your own custom issue types. Before you create a new Issue Type, you’ll need to decide on the names of Issue Types you need.
Types are: defect, issue, task, ... So to summarize it: Find your glossary that helps you. Define the scope you will address and include only work item types or issues that fall into that scope. Define a workflow for all of them, and keep that as simple as possible. Define the allowed relations between work item types, that help you track the ... Jun 10, 2016 · JIRA Issue Type Scheme with Defect subtask type. Once this is in place defects can be raised as subtasks of the story/bug that is being tested. Bugs can continue to be raised as Bugs in the normal way. The immediate benefits can be felt: It is obvious which issues are defects and which are bugs. Defects are directly associated with their ...
A web item might define an individual item within a JIRA drop-down menu or a button on the issue operations bar. A web section module defines a collection of links that is displayed together at a particular location of the JIRA user interface. The Epic issue type (and a few others) are added to a base JIRA installation when you install the "JIRA Agile" extension/plugin. None of the features (Epic Links, Epics filtering on backlogs, Epic burndown charts, etc) will work with any other issue type. I'd suggest you begin adapting your process to use the new issue type.