/
Jira Concepts

Jira Concepts

A Concept is an idea of something formed by mentally combining all its characteristics or particulars; a construct. We have many unique and innovative concepts in Eshopbox Jira software that simplify the life of our users. Please invest a little time in understanding these topics to get the most out of the application.

Project
Jira Software projects are flexible working spaces that allow you to group issues pertaining to a particular team, business unit, modules, or stream of work, together. For example, if you group your issues by modules, you could be allocated to one of the following;

  • Payment Reconciliation Engine

  • Product Engine

  • Integration Engine,

  • Fulfill Engine

  • Platform Engine

  • Integration Engine

  • Process Engine


Versions
A version is a set of features and fixes released together as a single update to your application. Assigning issues to versions help you plan the order in which new features for your application will be released to your customers. 


Sprint
A sprint is a short (2 weeks) period in which the development team implements and delivers a product increment for a project. A single project can have only one sprint ongoing at a time.


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:

Stakeholders of an issue
In Jira, there are 2 types of stakeholders to an Issue;

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

  2. 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.

Learn about the Jira Eshopbox hierarchal structure and flow

 

All SDE-IIs are required to ensure that their team members follow the Jira rules and guidelines strictly.

Related content