As we previously discussed what is Jira and its basic history, Now let us move towards the next steps i.e “Issues in Jira”.
Without issues, Jira is nothing just a blank template, so in the general term, we can say that “Issues” are the heart and soul of Jira. If there are no issues then there is no use of the Jira Tool. So let us see what we can refer to as Issues in Jira.
- It can be like project Task
- A helpdesk or Support Ticket
- Software Bug
- Internal Task
Jira provide by default 5 issue types and you can also create own issue type if you have Jira admin permission to customized your issues as per your business need.
- Epic
- Story or User Story
- Bug
- Task
- Sub-Task
Now let’s see one by one
1. Epic:
It is a big body of work and can be divided into a small body of chunks (stories) and often called issues in Jira. It can be created in the project as per the requirement of the project and also it can be tracked on multiple boards. Epic can be delivered in a set of Sprints.
2. Story or User Story:
Story is a small part of the issue type which can be created by the user as per the need. we can also call a story sometimes a “user story”. The smaller chunk of Epic is called stories.
3. Bug:
Bug is also an issue type, We can define bug when there is any blockage or problem which is stopping the functionality of the product then the user (Reporter) can create a Bug.
4. Task:
It is also an issue type that represents work need to be completed.
5. Sub- Task:
It is a sub-part of Task or we can say that Task is a parent and “Sub-task is a child. Subtask issues can be divided into any of the issue types like “Stories “, “Task”, “Bug”, and sometimes it can be your customized issue type.
Below screenshot shows all the issue type in the project:
If you found this article useful please provide your valuable feedback in the below comment box EduTaxTuber!
