The following are avaliable available issue types that we have in our Jira Instance Instance and its definitions. You can use any of these issue types based on your project needs. We also create custom issue types upon request, if the following does not meet your project's needs.
| Issue Type | Purpose |
|---|---|
| TASK | A task that needs to be done. A task is a unit of work contained within a story. In JIRA Agile, individual tasks are represented as sub-task issues, and stories are represented as (parent) issues. |
Subtasks is a smaller task within a larger piece of work. Sub-tasks are ones generally used to split up a parent task into a number of tasks which can be assigned and tracked separately in a project. | |
| STORY | A functionality request expressed from the perspective of the user. User story is a software system requirement that is expressed in a few short sentences, ideally using non-technical language. In JIRA Agile, a story is represented as an issue, and individual tasks within the story are represented as sub-tasks. |
| BUG | A bug is a problem that impairs product or service functionality. |
| EPIC | A large piece of work that encompasses many issues. It is essentially a large user story that can be broken down into a number of smaller stories. It may take several sprints to complete an epic. In JIRA Agile, an epic is simply an issue of type "Epic", with which other issues can be linked. |
| IMPROVEMENT | An improvement or enhancement to an existing functionality or tool. |
| NEW FEATURE | A new feature request, which has yet to be developed. |
| TEST | This Issue Type is used to create Zephyr Test within Jira. This issue is meant to be used for testing purposes manually and it does not offer automated testing. |
| REPORT REQUEST | For reporting projects. This issue can be used as an intake for report requests |
| NEW REQUEST | A new tool or development request. |
| REBUILD | Rebuilding a report, form or tool |
| BUSINESS TASK |
| Used for pilots or can be used based on the project need. |