How to use JIRA?

Let’s see how to use JIRA, from the very beginning(creating an Atlassian account).

Step 1: Creating an Atlassian Account

1. Go to the signup page of Atlassian enter the required user credentials asked on the site and then click on the SignUp button.

Signup Page

2. To complete the setup and login, click the verification link in the email box.

3. Set up your Atlassian account.

Page after clicking verify in the mail

4. Click on signup after filling details. The account has been created. The user is automatically redirected to the home page.

Home page

Step 2: Creating a new Project

1. Log in to your Atlassian account.

2. On the home page click on the Jira software and fill required details.

Jira Software

3. Answer some basic questions asked there to set up JIRA personally for your team.

4. Select your project name and template framework like Scrum or Kanban, etc. for your project.

Project Details

5. After completing the above steps, the following screen will be displayed:

Jira Software Home page

Four main sections are there:

  • Roadmap: It is an action plan for how our project will evolve.
  • Backlog: It is usually a list of issues describing what your team will be doing on the project.
  • Board: It shows work to be done, work in progress, and work done.
  • Code: In this, we can create an automated DevOps workflow and minimize context switching between Jira Software and Bitbucket, GitHub, GitLab, and other source code management tools.

Generally, a project is divided into epics and one epic can contain multiple sprints. Each sprint has multiple issues like user stories. A sprint is a fixed period (it can vary from project to project but in a single project, the duration of each sprint should be the same) in a development cycle where the project team completes work from the product backlog. JIRA’s user stories are concise representations of the system’s evolving capabilities, written by people who need that new functionality.

Now we have to create an epic first. So click on create select the issue type as epic fill in other requirements and create your first epic. Now create another issue “user story” to implement the first functionality for example register functionality of your project. Now move this issue to the already made sprint and start the sprint. Now your first sprint has started. We can also assign epic to the different issues.

What is JIRA Software?

JIRA is a software development tool used for project management and issue tracking. It is a popular tool among software development teams to plan, track, and release software projects. JIRA provides a centralized platform for managing tasks, bugs, and other types of issues and it helps teams to organize and prioritize their work. The tool integrates with other software development tools and has a variety of customizable features and workflows that allow teams to adapt it to their specific needs. Additionally, JIRA also provides various reporting and dashboard features that help teams stay on top of their work and make data-driven decisions.
JIRA supports multiple languages including English, French, etc. It is a platform-independent tool. A 30-day free trial version is available on JIRA. 

The following topics will be discussed here:

Table of Content

  • What is JIRA Used for?
  • How to use JIRA?
  • JIRA Scrum vs JIRA Kanban
  • JIRA Scheme
  • System Administration
  • JIRA Issues and Issue Types
  • JIRA Issue Attributes
  • How to Create an Issue in JIRA?
  • JIRA Components
  • JIRA Screen
  • Sub-Task
  • WorkFlows
  • Plug-ins in JIRA
  • Reports in JIRA

Let’s start discussing each of these topics in detail.

Similar Reads

What is JIRA used for?

JIRA provides a centralized platform for managing tasks, bugs, and other types of issues, and it helps teams organize and prioritize their work. JIRA is designed for agile software development teams and it supports multiple methodologies such as Scrum, Kanban, and custom workflows....

How to use JIRA?

Let’s see how to use JIRA, from the very beginning(creating an Atlassian account)....

JIRA Scrum vs JIRA Kanban

Kanban vs Scrum discusses two different strategies for implementing an agile development or project management system. Kanban is continuous and more fluid, while Scrum is based on structured short work sprints....

JIRA Scheme

A JIRA scheme is a collection of values ​​that can be used in one or more JIRA projects. And that is the strength of the scheme. A configuration you’ve been working on for a long time can be done once. As soon as the next project with the best configuration is created, you can apply the created scheme to the new project with just a few clicks....

System Administration

JIRA offers several useful features for administrators and users:...

JIRA Issues and Issue Types

In JIRA, an “Issue” is a unit of work that needs to be tracked, such as a bug, feature request, task, or any other type of work item....

JIRA Issue Attributes

Attributes represent specific information attached to an object. A description of that object, its model number, another associated object, or the user assigned as the owner of the object.Attributes can contain different types of information, such as text values, numbers, or references to other objects. It can also be customized to include very specific information. A postal code, a specific string pattern, a specific type of object, or a required value.Each object contains four default attributes. The attribute is set as the object’s label, the object’s key, when the object was created in Assets, and when the object was last modified....

How to Create an Issue in JIRA?

1. Select the blue colored Create button located on the top of each page....

JIRA Components

A component is a subsection of a project. These are used to group issues into smaller sets within a project. For example, a team can use components to group issues that describe work on a particular data object, service, plugin, or API within a project....

JIRA Screen

This is the placement and appearance of the fields displayed in the user interface when creating new issues, modifying existing issues, and transitioning issues from one state to another. When a user logs in as an administrator and navigates to Settings > Problems > Screens, all available screens are displayed. The screenshots below show the screens available for different projects. By clicking three dots, the user can see all the fields available on this screen. On the other hand, organized orders are displayed in the user interface....

Sub-Task

JIRA administrators can create subtask issue types to divide larger units of work into tasks that teams can assign and track individually. Subtasks are enabled by default. However, if your team only needs to work with standard issue types, you can turn them off....

WorkFlows

JIRA uses workflows to track the lifecycle of issues. A workflow is a record of states and transitions throughout an issue’s lifecycle. A status represents the status of an issue at a particular point in time. An operation can only have one status at a given time. For example: Open, To Do, Completed, Closed, Assigned, etc. A transition must exist for an operation to switch between two states. Simply put, migration is a type of work on a problem, and status is the impact of working on that problem....

Plug-ins in JIRA

JIRA plugins are software that users can install to improve the functionality of JIRA. These are commonly referred to as “apps” or “add-ons” at Atlassian. There are over 3000 unique plugins and nearly 1000 vendors in the Atlassian Marketplace....

Reports in JIRA

In JIRA, we can see different reports of our project by enabling report features inside project settings. It shows different reports like burnup reports, burndown reports, velocity reports, etc. Here is a short description of some of them....

Contact Us