Setting up JIRA

Go to following link-

https://www.atlassian.com/software

Then click on Try Free (blue colored button on top right of the page)

All products of JIRA will shown as follows-

Now among them select Try Cloud of Jira Software. So following page will shown-

Now click on Try it free button of Jira Software section i.e. first one from above image-

Now fill the form as follows-

Click on Agree and Sign up button.

Now Atlassian will ask you few questions. You can either select them or skip them. I here skipped them.
They Atlassian will ask you to invite some team members. We will also do it later. Now just skip this
section too.
They Atlassian will ask you whether you are new or experienced in JIRA, Agile methodology etc. as
follows-

Basically they ask this for recommending you a project type.

Click on Next button

Now following page will appear-

We see that Atlassian recommended us Scrum project.

If we suppose to skipped the previous section i.e.- following section

Then we will not see the recommended section. It will only show the following –
Now from above list click Select button of Scrum to pick Scrum type project

So following page will appear-

Now inside the text box we entered Name of the project to My First Project and then click on Create
button.

So the project is created as shown as follows-

It taken us to backlog page of our project as shown in above image.

So we have our first project in JIRA. We didn’t required any credit card for this.
Create a JIRA project with Sample Data

Go to the star(*) located on the top left corner as shown below-

Then after clicking on the Star(*) button we’ll see that there is a board already created as shown below-
Which means that JIRA has already created a board for our first project.

Now click on View all boards located as follows-

That will take us to following page-

Now click on Create board button which is shown above screen (the blue colored button on right of the
page). So following dialog box will open-
Now here inside the dialog box we have two types of boards [Scrum board and Kanban board]. Here we
have the option of creating the board using Sample data as highlighted below-

Note: we have to logged in as an administration to see both of those options i.e. create board using
sample data.

Among them we’ll select Create a Scrum board with sample data so following page will appear to us for
enter project details-
Here JIRA suggests a name for Sample project which is Sample Scrum Project as well as it’s project key
(is a unique key to identify the project in JIRA) and lead name. We’ll keep all of them and click on Create
board button as shown above image (bottom right corner- blue colored button)

After clicking on Create board button our board JIRA will create a brand new project with name Sample
Scrum Project (with sample data). So the backlog of the project will shown as follows-

Now we have a backlog with some sample data. Now we’ll go through with them.
Agile Scrum Refresher

Agile is a software development methodology that has an iterative approach to development. Basically
building and releasing software incrementally from start of the project rather than trying to deliver
everything at the end.

This iterative approach involves planning a development iteration implementing the work planned for

Kanban Refresher

JIRA Terms

Issues

▪ Essence of JIRA
▪ Represents any work item that requires an action to taken from a person
▪ Each ticket in JIRA is an issue i.e. when we create a ticket in JIRA we actually create an issue
▪ Epics, stories, bugs, features, tasks etc. all of these are issues
▪ Issues can be of different types like-
o Epic Issue Type
o Story Issue Type
o Bugs Issue Type
o Task Issue Type
o Custom (anything chosen by user) issue type i.e. user can create any issue type in JIRA as
needed
▪ Each issue contains basic fields such as
o Title
o Description
o Due Date
o Priorities
o Status
o User Chosen Custom field i.e. user can make any custom field for an issue

Projects

▪ Collection of Issue
▪ Can be a software development project, Help Desk System project, General Task Management
Project etc.
▪ When we are working with JIRA Agile/JIRA software which means that we are essentially
working with software development project
▪ Everything of a project can be customizable which means that
o Custom Access Privileges
o Custom Issue Types
o Custom Workflows etc.
Workflow

▪ Set of statuses that an issue of a project can have and the issue go through those statuses during
it’s start to completion i.e. an workflow is the road map for an issue. Issue go through that
roadmap during working with that issue. The start of the road indicates the work of the issue
need to start. The middle of the road indicates the issue is in working state/ in progress state.
The end of the road indicates that the work for the issue is done.
▪ Following is a workflow of an issue-

▪ When we create an issue/ticket in JIRA it goes into the To Do Status

▪ If we initiate the transition i.e. start the progress it will go to In Progress Status or we can initiate
the transition to Done which will take the issue to Done state
▪ Transition in JIRA represented by button in issue details page
▪ If the issue is currently in the In Progress state or with that status then we will see two buttons
whose are
o Stop : when we will click on Stop button our issue will back to To Do status
o Done: when click on Done button it will take me to Done status
▪ If the transition is done then we will have a button for re-open the ticket. In case of reopen it
will have a button for start progress. Similarly when click on start progress the issue will go to In
progress state.

Versions

▪ Help to track the releases of the software.

▪ For tracking purpose JIRA allows to create a version and add whatever issues are going to
release in that version
▪ If we release after each sprint then we can create version after end of each sprint. On the
other hand we can create a version over a set of sprints then we can create version before
release them.
 ▪ In Scrum a version is pre planned and is released when the planned work is complete
▪ In Kanban a version can be released at any time and will contains all issues that are
completed or in the Done state at that time

Components

▪ Sub section of a project

▪ Uses to group the issues of a project
▪ Example
o Projects are broken into backend and frontend
o Create backend as a component and frontend as another component
o By this way we can be able to group our issues
▪ Almost like category of a work
▪ We can configure issues those are created under a component to have a default assignee so that
when created it automatically assign to assigned person
▪ Example
o Assign all backend issue to lead backend developer
o Lead developer will then delegate them to other developers

JIRA UI & Navigation

Now we’ll look the JIRA UI and high level navigation flow.

When we log into JIRA for the first time we’ll see our system dashboard as shown below-
The Dashboard contains different informations. Each individual boxes are known as gadgets. We can
customize the entire dashboard and add different pieces of information those are relevant.

Inside above dashboard there have Assigned to Me, Activity Stream, Projects etc. gadgets. Assigned to
me gadget displays the information those are assigned to me. Activity stream is like a news feed that
tells what is being going on the site. This is the system dashboard which is create for us by default.

We can also customize this dashboard and share it among other team members.

The dashboard appears inside the main content area as shown below

On the left side of the dash board there have a navigation bar as shown below-
Let’s have a closer look on sidebar
JIRA Project Navigation

Go to Home page by clicking square ( )

It will show following things-

▪ Projects
▪ Dashboards
▪ Issues and Filters
▪ Jira Settings
Now click on the Projects

It will show the list of projects as follows-

The tile form shows most recent visited projects for quick access

The list shows all lists of the project that the user have.

Inside the list it contains-

▪ Name : Name of the project

 ▪ Key : Unique identifier of the project. It also helps to create unit issues like SSP-1, SSP-2 etc.
▪ Type : Determine the type of project e.g. software project, business project etc.
▪ Owner : determines the person who created the project
▪ Category: optional feature that uses to categorize the project. Using to organize our project
Example- we have a project to handing and tackling bugs and another project which uses to
develop new features. So we can categorize them accordingly
▪ URL : optional feature. We use it to easily access the project
Example- we are building a website and we are managing it through a JIRA project then we can
provide that URL so that we can access easily

At the top of the page we have a button (blue colored) called Create Project ( ). Only
for admin user or those users who has the permission to create project will be able to see the button. So
it the button doesn’t visible to any user that’s means that the user doesn’t have permission to view the
button.

Now click on the project name. it’s a link.

When click the link it will open following board-

It’s a task board. On the left of the task board the menu is showing.

Let’s see all menu items.-

On the top it’s a project switcher. If we click on the drop-down it shows all available project and we can
switch from one project to another as shown below-

Within a project we have some menus whose are-

▪ Board of the project

▪ Backlog of the project
▪ Active Sprints of the project
▪ Reports
▪ Releases
▪ Issues and filters
▪ Pages
▪ Components
▪ Add Item
▪ Project Settings

SSP board

▪ If we click on SSP board the board will appear as follows-

▪ We can also switch from one board to another as follows-

Backlog
When click on backlog it will show the backlog of this project as follows-
Here we can also see the epics, versions, active sprint and backlog items etc.

Active Sprints
If we click on this menu it will show all items of the Active Sprints as follows

Reports
Uses to view all reports of the project like burndown chart, burnup chart, team velocity
reports etc.
Releases
Uses to view the list of all releases-

Issues and filters

Uses to browse and navigate all the issues under the project as follows-
 Components
Uses to categorize the items in JIRA
Add Items
Uses to add items like issues
Project Settings
Setting the projects. Only can be seen by admin

13. Issue Navigator

Go to home page by clicking square icon ( ) located on the top of the menu bar.

Now click on Issues and filters menu as shown below-

Here it will show the sub menues as follows-

From the submenu (1) either I can click on search issues for a brand new search or (2) I can select some
of the existing filters.

Click on Search Issues i.e. (1) and that will take me to the issue navigator page as shown below-
In the left it displays the list of issues. We can navigate one by one either by using mouse or arrow key.
The corresponding issue detail appears on the detail pin / detail column which is located on right side as
shown below-

At the top of the page we have a bunch of filtering options as shown below-
Once we have select a set of filters we can also save that filter which can be managed by using clicking
Save as option available at following location-

We can also share the filter and export the filter in bunch of different format by clicking either on Share
icon or export icon as shown below-
14. Viewing, editing and understanding Issues
15. Working with Agile Board

Go to home page by clicking square icon ( ) located on the top of the menu bar.

So following page will appear-

We are currently work with Sample Scrum Project. So click on it. So following board will appear to us-

The overall details are given below-

Now to see the details double click on a issue. So a popup will shown with details information of the
issue as follows-
16. Agile Board- Backlog View

When login to JIRA following Dashboard will shown-