/
Issues

Issues

Owned by Rishabh Khanna (Unlicensed)
Last updated: Aug 19, 2020 by Akshay Aggarwal (Unlicensed)
3 min read

What is the purpose of the Article?

  • You will understand what are the issues used in Jira in Eshopbox

  • You will understand what is an issue status and its types

Audience

  • Product Managers

  • Software Development Engineers

What is an Issue?

A Jira 'issue' refers to a single work item of any type that is tracked from creation to completion. For example, an issue could be a feature being developed by a software team, a to-do item for a marketing team, or a contract that needs to be written by a legal team.

The following Issue types are used in Eshopbox:

Epic
Each EPIC is part of a project and deeply, a collection of user stories. The idea is to break work down into shippable pieces so that large projects can be completed and users can deliver continuous value to customers.

Task
A TASK is created under an EPIC to organize the planning for a User Story. This involves creating Research Documents, Help Articles, Business requirement documents, and other frameworks to plan and analyze the requirement.

USER STORY
The purpose of a user story is to articulate how a piece of work will deliver a particular value back to the customer. It is a small unit of work in an agile framework and comes under an Epic in Eshopbox. A single user story usually corresponds to one user journey.

Sub-task
A User Story is completed by performing multiple tasks within teams and amongst different teams. To track the progress in each team, sub-tasks are created and assigned to the concerned person. A Sub-Task contains a description of individual work (detailed or technical) that is required to achieve the goals of a user story.

Bug
A problem that impairs or prevents the functions of the product. A Bug could arise due to multiple reasons. For e.g/- Change in the business requirement, Change in technical flow, non-handling of edge cases, etc.

Issue status and workflow

Each issue type has its own unique workflow in Eshopbox which is governed with the help of Statuses. The status of an issue implies that at what point the issue is placed currently, during its life-cycle. In Eshopbox, each Issue type has its own set of statuses which together constitute its workflow. Also, you can create custom issues according to your needs.

Issue statuses currently used in Eshopbox are as follows:

  • To do: Each issue type has its initial status set to “To do” by default upon creation. This status implies that the issue still needs to be taken up by an assignee.

  • In Progress: This status implies that the assignee is currently working on this particular issue.

  • Under Review: This status implies that the quality checks/testing for this particular issue is pending.

  • Done: This status implies that the issue has been completed by the assignee.

Stakeholders of an issue
There are 2 types of stakeholders to an Issue;

  • REPORTER:

    • A reporter is the one who has created an issue type and should be in constant touch with the assignee.

  • ASSIGNEE:

    • An assignee is the one who is responsible for completing the issue type.

The stakeholders are responsible for navigating an issue through its workflow with the help of different statuses

Related content