Brief About The Issue Type In Jira

Brief about the EPIC, STORY,TASK and BUGS

These are the most important terms which we use in JIRA, Below are the description of these terms.

EPIC: - In simple terms, we can define the epic the combination of two or more than 2 stories.

Basically epic is the large part of the stories, collection of stories made an epic.

Epics are usually broad in scope, short on details, and will commonly need to be split into multiple smaller stories before the team can work on them.Epic contains stories that can be one or more than one.

STORY: - A story or we can call it user story, it is basically the software requirement which we write in the JIRA in some short sentences.

We write the stories in nontechnical language, basically, we made developer understand the requirement in non-technical language. The story contains the task. A story is a detailed version of the task.

Task: -  Task is a unit of work contains in the story. A story may have more than one task.

In JIRA individual tasks represent a subtask Issues and story represent as parent issues.

We assign the task to the developer in which elaborate the particular functionality.

Bug: - A bug is an error in the software system, that means which deviates from the flow of the requirement which give us the wrong or incorrect result.

Any unexpected behavior or anything which is not equal to the expected, when the flow of the application or any functionality result is not equal to the expected result when our actual result is not equal to the expected then the bug arises and this behavior is called the bugs.

If we talk in a summarised way then we can say Epic contains story and story has the Tasks and if Task is not executed correctly the flow is different from the task then it arises the bugs.

In the below image we can see the Epic has story and story has the tasks.

Thanks!!