JIRA is developed by an Australian company called Atlassian. It is a project management tool used for planning, tracking, reporting, and release. The word “JIRA” is derived from the Japanese word “Gojira” which means “Godzilla”.The basic use of this tool is to track issues and manage software projects.

Some of the terminologies used in JIRA are epic, story, task,sub-task, and bug.

Epic

The epic represents a group of stories. They are used to describe the group of related issues.

Story

The story represents a group of tasks. It is a tool used to capture the description of software from an end-user perspective.

Task

Task represents the group of sub-tasks. Thus it represents the work that needs to be done

Sub-task

Sub-task represents the individual process of a task. It represents the piece of work that is required to complete a task.

Bug

Bugs represent the errors/defects in the code. They have an impact on the project depending on whether it’s a major bug or a minor bug.

Let’s discuss the complete workflow of JIRA software in this blog.

The JIRA software can be explained in the following phases,

1) Creating a task in JIRA

2) Bulk import in JIRA

3) Quick filter in JIRA

4) Working against task

5) JIRA – issues and filters

6) Board setting in JIRA

7) Project setting in JIRA

8) Swimlanes in JIRA

CREATING TASK IN JIRA

In JIRA dashboard, there are three columns namely,

1) To do

2) In progress

3) Done

TODO

In this column, tasks to be completed are included

IN PROGRESS

In this column, tasks which are in progress are included

DONE

In this column, tasks which are finished are included

These columns are available by default. Apart from these columns, we can also add custom columns in the list such as Dev-complete, Ready for QA, In QA, Icebox, Backlog and Done.

BULK IMPORT IN JIRA

Bulk import in JIRA represents the tasks uploaded using a CSV file.


QUICK FILTER IN JIRA

A quick filter is used to filter the sprints in a project by giving the search keyword in the search box. We can add or delete components through the filter. We can easily track the project using components.


WORKING AGAINST TASK

If a task can’t be completed within the stipulated period of time, then the task can be marked as a flag. Thus, other tasks can be completed by putting the difficult task on hold. The hold task can be completed later by giving remove flags.

When the task is completed partially then the time spent should be marked in log work. The list of tasks that are completed partially is entered in the comments section.


JIRA – ISSUES AND FILTERS

JIRA filters are used to search the columns based on components, assignee, time spent and updated date. Thus, we can export the data as CSV/excel after applying a filter to the list.            



BOARD SETTING IN JIRA

The JIRA board can be customized in settings as general, columns, swimlanes, quick filters, card color, card layout, estimation, working days and issue detail view.


PROJECT SETTING IN JIRA

The projects in JIRA can be customized in settings as details, people and summary.

DETAILS

Details of the project such as project name, key, assignee and team lead are changed here.

PEOPLE

People who are working in the project can be added/removed here. They can be given roles such as developers/administrators.

SUMMARY IN JIRA

Fields such as Issue types, versions, workflows, components, screens, roles, fields, permissions, settings, and notifications can be changed here.

SWIMLANES IN JIRA

When there are multiple contributors in a single project, then the tasks are allotted to them as directories. When the developers are working on an individual project, then the tasks are allotted through the assignee. Thus, swimlanes are useful to split up the project between developers.

KANBAN

KANBAN is a Japanese word that means billboards. It was used by car manufacturing companies like Toyota in the 1950s to maintain details of spares required to assemble a car. Later it came into existence in the software industry which works in the same principle. Kanban maintains the list/record of requirements obtained from the clients. This saves time and cost of the project by limiting the resources.