EX.

NO: 01
INTRODUCTION TO JIRA

AIM:

To study about the JIRA tools and its applications.

DESCRIPTION:

INSTALLATION OF JIRA TOOL

• JIRA follows the Client/Server concept. At the server side, JIRA must be installed
before using it as end user.
• At the server side, JIRA must connect with relation database to store issues/application
data.
• Download the JIRA Windows Installer.exe file.
• Select the OS type and click on Download.

• Run the .exe file to run the installation wizard.

• After clicking the .exe file, the Run confirmation pop-up displays, click on RUN.

• click on Next.
• Choose the appropriate installation option and then click on Next.

• The installation summary is displayed with the Destination Directory, Home Directory,
TCP Ports, etc.,
• Click on Install. JIRA will start installing.

• After installation, JIRA will be started automatically if the check box to “Start JIRA
Software 7.3.4 now” is checked. Then click on Next.
• Click the Finish button.
JIRA

• JIRA is a software testing tool developed by the Australian Company Atlassian. It is a

bug tracking tool that reports all the issues related to your software or mobile apps. The
word JIRA comes from the Japanese word, i.e., "Gojira" which means Godzilla.
• JIRA is based on the Agile methodology and the current version of the Jira is 6.

Useful aspects provided by the Jira:

• Projects: It is used to manage the defects very effectively.

• Issue: It is used to track and manage the defects/issues.
• Workflow: Processes the Issue/Defect life cycle. Suppose we have a business
requirement, we create the technical design and from the technical design, we
create the test cases. After creating the test cases, coding is done, and then
testing is performed on the project. This design workflow is possible by using
Jira.
• Search: Find with ease. Suppose we have done with a project at the beginning
of the December and its version is 1.0. Now, we move to version 1.1 and
completed at the end of December. What we are doing is that we are adding new
versions. Through Jira, we can get to know that what happened in the earlier
versions, how many defects occurred in the earlier projects and the learning we
achieve from the earlier projects.
 • Dashboards: Dashboard is a display which you see when you log in to the Jira.
You can create multiple dashboards for multiple projects. You can create the
personal dashboard and can add the gadgets in a dashboard so that you can keep
track of the assignments and issues that you are working on.

Applications And Uses Of JIRA

• There are various uses of the JIRA tool, which one can easily find in the market.
However, some of the most important applications of the JIRA tool that are
considered in the companies are stated below.

JIRA For Project Management Teams

• JIRA tool can be a lot more useful for project management teams. It is highly
compatible, and one can configure it with any type of project. The compatible nature
of the JIRA tool is what made it popular in the market. For project management
teams, the JIRA tool provides tons of project templates to choose from.

• A team can even create their own templates on which they can be designed their own
workflow. JIRA program software tracks make sure that all the pieces of work pass
through the workflow so that all the steps are completed.

• Moreover, the admins can even get to see who is doing what type of task in the
project and accordingly track the progress of the task. The project templates provided
by JIRA program store everything, from reports to workflow, and even track progress.

• This makes it comfortable for the project manager to view everything at a single place
and point out the things that need to be done.
OUTPUT:

RESULT:
Thus the study and the installation of the JIRA tool has been completed successfully.
EX.NO: 02
BACKLOG ITEMS IN JIRA

AIM:

To study about the backlog items in JIRA tool.

DESCRIPTION:

BACKLOG

• The Backlog in JIRA is nothing but simply a list of requirements or features of that
given software application, where the features of the application are not described in
detail in the backlog.
• It is mainly described the list of tasks in the form of user stories with specific priority
status i.e. brief description on each functionality of the software application from the
user perspective.

CREATING A BACKLOG IN JIRA

• Click on “Backlog” Icon.

• Fill the details in the create issue page i.e. select the name of the project, select

Issue/task Type(It may Bug or Epic or Story), Write down Summary for

Issue/task(Overall description), Description about it, Priority level(Low or Medium or

High), Labels, Environment, Attachment related task, Linked Issues, Assigned To,

Epic Link, Sprint, etc.

• Click on the “Create” button to create a new Backlog.

Activities Performed by Backlog in JIRA

There are multiple activities are performed by the backlog in JIRA tools. Such as adding of

tasks or issues to the backlog, description of the task, to prioritize the task, create the task of

the task (subtask), workflow status of backlog, finding of task or issue or deleting of task or

issue and split of the task, mode of the transition of backlog and status of team workflow.

• We can add a task or an issue to the backlog in the JIRA tool by creating an issue/task

with adding some parameters related to it and then the task will be created in the

backlog list i.e. the team will start work on it. The issue in the backlog may be bug or

story or epic (a big requirement).

 • The tasks which are present in the backlog, it showing the description or short

summary about it. From that, we exactly have known the actual or excepted criteria

about the tasks or issues.

• According to the severity of the bug or story or epic, the priority will be set to each

task in the backlog. The priority levels will be set to the tasks may be low or medium

or high. The high priority backlogs should adopt first for resolve in the first sprint and

so on.

• We can create a separate task inside the existing task is called a subtask. The subtask

also added to the backlog with priority level. For a big task or a task not completed

within the time then we go for this concept.

• It showing the workflow status of each task in backlog i.e. the status report of project

improvements or testing status of the application.

• From the backlogs, we find the total number of tasks or delete any unwanted tasks or

split the tasks as per the scope of the software application. So it is easy to track all the

records about it.

• It provides the status of work progress of each task or issues i.e. in To Do stage or In

Progress stage or Done stage. It shows how many backlogs in complete mode or

progress mode or to be done mode.

• It provides the status report of the teamwork i.e. who involves resolving

in which backlogs or how many tasks are completed by whom or who assigned for the

tasks. It tracks team workflow status.

Advantages of Using Backlog in JIRA

• It provides outstanding works for the development software application.

• It can handle the software requirements, sprint planning, and defect handling.
 • It provides proper prioritization for the tasks so the software will develop in the way.

• It is used to track the project improvement flow, defects/bugs workflow, and team

workflow.

• It supports the creation of subtask for a given task and represents the status of

transition flows of the task i.e. to do or in progress or done.

• It helps to choose the backlog tasks or issues to make newsprint design.

• It provides a plan for the design of software applications.

• It will help in finding all tasks or issues or even to delete some tasks.

• It helps to create new issues or tasks and added to the backlog.

• It needs to develop a software application with high priority features.

OUTPUT:

RESULT:

Thus the backlog is created and studied successfully.

EX.NO: 03
CREATING A PROJECT IN JIRA

AIM:
To create a project in JIRA .

DESCRIPTION:

PROJECT MANAGEMENT IN JIRA:

• Project management is a practice that involves planning, executing, and monitoring

all of the processes and tasks required to reach a set business goal.
• While all three versions of Jira Core, Software, and Service Desk are robust project
management tools, Jira Software is required to take advantage of Jira’s agile
capabilities, like Scrum and Kanban boards.
• Each task in Jira Core has all the relevant project and task details in one place
including: which team member is working on it, collaborative comments and
feedback and due dates.
• As a result, each team member has visibility on the entire project.

CREATING A PROJECT IN JIRA

• Choose Settings > Projects.

• Select Create project.
• Choose Company-managed project.
• Give your project a name.
• To change your project template, select Change under Template. Then, select one of
the available project templates (e.g. scrum software development).
• Project templates appear based on the Jira products you have subscribed to. For
example, if you subscribe to Jira Service Management, you can create projects using
the IT service desk and Customer service desk templates.
• You can also create a project with a shared configuration to use the permissions,
workflows, issue types and other schemes from an existing project.
 • You can also import a project and its issues from other tools. See Migrating from other
issue trackers for more info.

• Once you select a project type or an existing project for shared configuration, click
Create.

• If you're creating a project using a template related to a Jira product you currently do
not have access to, Jira will display a checkbox that will allow you to grant yourself
access to that application.
• This will add you to the default group of that application, and you will count as a user
for that license.

OUTPUT:

RESULT:

Thus the project is created successfully in JIRA.

EX.NO: 04
DASHBOARDS IN JIRA

AIM:
To study and create a dashboard in JIRA.

DESCRIPTION:

DASHBOARD

• Dashboard is the main display you see when you log in to Jira.
• You can create multiple dashboards from different projects, or multiple dashboards for
one massive overview of all the work you're involved with.
• You can create a personal dashboard and add gadgets to keep track of assignments and
issues you're working on. Dashboards are designed to display gadgets that help you
organize your projects, assignments, and achievements in different charts.
• To view all of your dashboards, choose Dashboards > View all dashboards.

DEFAULT DASHBOARD

• The default dashboard is the screen that all Jira users see the first time they log in.
• Any users who have not added any dashboard pages as favourites also see the default
dashboard.
• Jira allows Administrators to configure the default dashboard.
• The gadgets on the default dashboard can be re-ordered, switched between the left and
right columns, additional gadgets can be added, and some gadgets can be configured.
• The layout of the dashboard (e.g. number of columns) can also be configured.
• All changes made to the default dashboard will also change the dashboards of all users
currently using the default.
• However, gadgets that users do not have permissions to see will not be displayed to
them. For example, the 'Administration' gadget, although it may exist in the default
dashboard configuration, will not be visible to non-admin users.
• Gadgets are the information boxes on the dashboard. Jira comes pre-configured with a
set of standard dashboard gadgets.
• It is also possible to develop custom gadgets and plug them into Jira using its
flexible plugin system.
CREATING A DASHBOARD

You can create and customize your own dashboard to display the information you need. Only
Jira admins can customize the system dashboard.

• Choose Dashboards > Create dashboard.

• Name your dashboard and add a description so your team knows when to use
it.
• Fill out the remaining fields and click Save.

CREATING A DEFAULT DASHBOARD

• Select > System.

• In the User interface section, select System dashboard.
• Select ··· > Share dashboard.
• Select the dropdown under Viewers.
• Choose one of the following:
• My organization. Only people who sign in from your organisation will be able
to view the dashboard. Anonymous users won’t be able to access it.
• Anyone on the internet will be able to view your default system dashboard.
• Anonymous users will be able to access it.
• Select Save.

OUTPUT:

RESULT:
Thus the project is created successfully in JIRA.
EX.NO: 05
CONFIGURING GADGETS IN JIRA

AIM:
To create and configure gadgets in JIRA.

DESCRIPTION

GADGETS

• Gadgets display summaries of team progress, reports, and other data from Jira projects
and issues a dashboard.
• You can customize gadgets to display project and issue details relevant to particular
users.

ADDING A GADGET TO DASHBOARD

• You can add gadgets to your own personal dashboard(s).

• To add a gadget to the default dashboard for your Jira application, you must be a Jira
admin.
• Some applications allow dashboards that are shared by groups of people.
• If you have permission to update a shared dashboard, the other people sharing the
dashboard will see your changes, too.
• Go to the dashboard by selecting the Dashboards link in the header.
• If you don't already have a dashboard, select Manage Dashboards from the
dropdown, then Create new dashboard.
• Once your dashboard is created, on the dashboard, select Add Gadget.
• Use the gadget wizard to choose the gadgets you want to add. You can see a list of
these gadgets in Gadgets for Jira applications.
CUSTOME GADGETS
• You need administrator privileges to add a gadget to the list of available gadgets.
• If you have permission to add and remove gadgets from the directory itself, you will
see the 'Add Gadget to Directory' and 'Remove' buttons on the 'Add Gadget' screen.
• This functionality is only available for the Server version of applications; if you
would like to add an Atlassian gadget to a directory in your Cloud site, please contact
Atlassian Support.

CUSTOMIZE GADGETS IN JIRA

There are a few ways you can customize the view of gadgets in a dashboard:

To Do this

Expand or collapse gadgets Use the More ( ) button in the gadget

header.

Expand a gadget to take up the entire Use the Maximize ( ) button in the gadget
dashboard header.
Notes...

Rearrange gadgets
Use the ( ) button in the gadget
header.

Customize the gadget frames Use the More ( ) button in the gadget
Delete a gadget header.

ADDING GADGETS TO DEFAULT DASHBOARD

• Select > System.

• In the User interface section, select System dashboard.
• Select Add Gadget. To view all available gadgets, select Load all gadgets.
• Find the gadget you want to add. You can also filter the gadgets by searching for or
clicking a category on the left.
• Select Add gadget for the gadget you want to add.
 OUTPUT:

RESULT:
Thus the gadgets has been configured successfully in JIRA.
EX.NO: 06
USERS AND GROUPS IN JIRA

AIM:
To study and create users and groups in JIRA.

DESCRIPTION:

CREATE, EDIT AND DELETE USERS

• When you add a user to your Users list, you're inviting a user with that specific email
address to your site.
• If the user with that email address has an Atlassian account, they'll now be able to log
in to your site. If the user doesn't have an account, we'll walk them through the
Atlassian account signup process.
• Although they're logged in to your site, their account exists outside your site so that
they can use that same account to log in to other sites.
• Go to your site's Admin at admin.atlassian.com. If you're an admin for multiple sites
or an organization admin, click the site's name and URL to open the Admin for that
site.
• Select Invite users from the Users list page.
• Enter the Email address you want the user to log in with (you can enter more than one
at a time or a string of them using a space or comma.
• If you invite a user with a different email address from their Atlassian account email
address, and they end up creating a new Atlassian account, they can't combine the two
accounts.
• You'll need to re-invite the user with their original account and remove access for the
other account.
• If they create any content while logged in with the second account, that content will
still exist but will remain associated with their other account.
• Select where you would like to allow other users with this email domain to self signup.
• Select the Role you want these users to have on your site:
• Basic – Can access specified products and apps. No additional permissions.
• Trusted – Can access, configure, and add products. Can invite users.
• Site administrator – Full admin permission for the site.
• Select products from the Products access list. When users get an invite, we'll add the
user to the groups for the products you select, so you can always change them later.
• Select Invite users(s).
CREATE , EDIT AND DELETE GROUPS

Create groups

• Log in to admin.atlassian.com.
• From your organization, select Directory > Groups from the left side of the page.
• Select the Create group button to create a new group.
• Enter the Group’s name, add the Group’s members, and enter the Group's
description.
• A group’s name cannot be changed after being created. You will need to create a new
group with a different name.
• Select Create.
• You’ll be redirected to the Groups details page where you can add products to the
group and give group members product access. Select Add products to view a list of
products.
• From the Product roles dropdown for a Product, select a product role.
• Select Add.

Edit and delete groups

• Log in to admin.atlassian.com.
• From your organization, select Directory > Groups from the left side of the page.
• Select a group from the list to edit or delete.
• Edit the group description by selecting the 3 dot icon to the right of Add group
members > Edit description.
• Edit the group's product access by clicking Edit group's access under Group access.
Learn more about updating product access settings.
• Delete the group by selecting the 3 dot icon to the right of Add group members
> Delete group.
OUTPUT:

RESULT:
Thus the users and groups in JIRA has been studied and executed successfully.
 EX.NO: 07
PERMISSIONS IN JIRA

AIM:

To study about the permissions in JIRA.

DESCRIPTION:

PERMISSIONS
Permissions are settings within Jira applications that control what users within
those applications can see and do. All Jira applications allow a variety of permissions from
whether users can create new projects to whether a user can see a specific type of comment on
an issue. These permissions can differ between applications.

TYPES OF PERMISSIONS
There are three types of permissions in Jira applications, and they range from the high-level to
granular

• Global permissions - These apply to applications as a whole, not individual projects

(for example, whether users can see the other users in the application).

• Project permissions - Organized into permission schemes, these apply to projects

(e.g. who can see the project's issues, create, edit and assign them). While project
admins can assign users to a project, they can't customize the permission schemes for a
project. There are lots of project-level permissions you can set to control what users
can do within a project.

• Issue security permissions - Organized into security schemes, these allow the
visibility of individual issues to be adjusted (within the bounds of the project's
permissions). For example, issue security permissions can let you set up types of issues
that can only be seen by project admins or users in specific groups.

ASSIGNING OF PERMISSIONS IN JIRA

• Permissions can be assigned to groups or to project roles/and or issue roles. This
diagram illustrates how permissions are assigned to users:
 Permission Can be set by more information

A user with the Jira System

• Managing global
administrator permission
Global permission permissions
A user in a group
with Admin access

• Managing project
A user with the Jira System
permissions
administrator permission
Project permission • Permissions for
A user in a group
company-managed
with Admin access
projects
A user with the Jira System
administrator permission
A user in a group • Configuring issue-
Issue security permission
with Admin access level security

A project admin
OUTPUT:

RESULT:
Thus the permissions in JIRA has been studied and created successfully.
 EX.NO: 08
USER MANAGEMENT IN JIRA

AIM:
To about user management in JIRA tool.

DESCRIPTION:

USER MANAGEMENT

User creation is the most important part of the User Management process, it is not
limited to just that.

The important user-related activities performed by a JIRA Admin are:

• Edit a particular user information

• Delete a user
• Creating users groups
• Creating Roles
• Permissions
• Setting Preferences
•

ADDING AN USER

• Click on the “Invite Users” button in the User Management->Users screen and enter
one or more email ID’s in the below dialogue that opens up. click Send.
• The invitation sent message comes up when the message is successfully sent.
• In case of an email invite, the user is not added until the recipient of the email invite
acts on the received invitation.

EDITING A USER

• Go to the User Management -> Users page. All the users available will be displayed.
The top portion of this page contains a “Filter” section.
• This can be used to manipulate how/what user information needs to be displayed. You
can choose to keep it empty, in which case it displays all the users available.
• Note the “Edit” link in the “Operations” column. Click on the corresponding “Edit”
link for the user whose information is to be modified.
• You will be able to change the following profile information
DELETE A USER

• Choose the “Delete” link corresponding to the user you would like deleted from JIRA.

A JIRA Admin can additionally:

• Configure the look and feel

• Configure workflows
• Set Project/issue-level security details.
• Can add custom fields/screens
• Integrate a JIRA project with development tools to make sure that the commit, revert,
changes, etc. can reflect immediately in JIRA.
• Configure Dashboard settings
• Set time/time zone information.
• Configure and set email preferences

OUTPUT:
RESULT:

Thus the user has been added, deleted, edited and managed in JIRA tool.
EX.NO: 09
PROJECT ROLES IN JIRA

AIM:

To study about project roles in JIRA.

DESCRIPTION:

PROJECT ROLES

• A Jira application project role is a flexible way to associate users and/or groups with a
particular project.
• Unlike groups, which have the same membership throughout Jira applications, project
roles have specific members for each project.
• Users may play different roles in different projects.

VIEWING PROJECT ROLE MEMBERS

• Go to your project and click Project settings.

• Select People.

ASSIGNING A USER OR GROUP TO A PROJECT ROLE

• Go to your project and click Project settings.

• Select People.
• Select Add people from the top right corner.
• Search for the user or group you wish to add, and select the project role you wish to
add them to.
• Browse users and groups global permission is required to search for existing users or
groups at this step. If you do not have this permission, you will need to specify the
exact name or email address.
• Select Add.

REMOVING A USER OR GROUP FROM A PROJECT ROLE

• Go to your project and click Project settings.

• Select People.
• In the user's or group's entry on the table, select Remove.
OUTPUT:

RESULT:

Thus the project roles has been created and assigned in JIRA.
EX.NO: 10
CREATE PROJECT ROLES IN JIRA

AIM:
To create a project role in JIRA.

DESCRIPTION:

MANAGE PROJECT ROLES

• Project roles are a flexible way to associate users and/or groups with particular
projects.
• Project roles also allow for delegated administration.
• Jira administrators define project roles — that is, all projects have the same project
roles available to them.
• Project administrators assign members to project roles specifically for their project(s).
A project administrator is someone who has the project-specific 'Administer Project'
permission, but not necessarily the global 'Jira Administrator' permission.

PROJECT ROLES CAN BE USED IN:

• permission schemes
• email notification schemes
• issue security levels
• comment visibility
• workflow conditions

USING PROJECT ROLES

• Project roles enable you to associate users with particular functions.

• Create a project role called Quality Assurance.
• Create a permission scheme called Software Development, in which you assign
the 'Close Issue' permission to the Quality Assurance project role.
• Associate the Software Development permission scheme with all software
development projects.
• For each software development project, add the appropriate Quality Assurance
people to the Quality Assurance project role.
DEFAULT PROJECT ROLES

• A system role is a specific type of default project role that's managed automatically by
Jira (for example the atlassian-addons-project-access role). Viewing project roles

VIEWING PROJECT ROLES

• Choose > System.

• Under SECURITY, select Project roles. The Project Role Browser displays, which
contains a list of all the project roles in your Jira site.
• To see where a project role is used, click the View Usage link. This displays a list of
the project role's associated permission schemes, email notification schemes, issue
security levels, and workflow conditions.
• Click any of the View links in the Project Role Members Per Project column to see
which users/groups are associated with a project role for a particular project.

ADDING A PROJECT ROLE

• Choose > System.

• Under SECURITY, select Project roles. The Project Role Browser displays, which
contains a list of all the project roles in your Jira site.
• Under Add Project Role at the bottom of the page, enter your desired role's name and
a description
• Click the Add Project Role button.

ADDING MEMBERS TO ROLE

• Click on Manage Default Members in the Actions column for your newly created
project role.
• Click Edit under Default Users or Default Groups.
• Enter group names in the Add user(s) to project role field. Or, select the user picker
icon to add individual users.
• Click the Add button.

DELETING A PROJECT ROLE

• To delete a project role, locate the project role in the project role browser, and click
the Delete link.
• The confirmation screen that follows lists any permission schemes, email notification
schemes, issue security levels, and workflow conditions that use the project role.
• Deleting a project role removes any assigned users and groups from that project role,
for all projects. Be aware of the impact this may have.
OUTPUT:

RESULT:
Thus the project roles has been created in JIRA.
EX.NO: 11
TEST PERMISSIONS IN JIRA

AIM:
To create test permissions in JIRA.

DESCRIPTION:

MANAGING PROJECT PERMISSIONS

• Jira administrators manage project permissions for company-managed projects through

permission schemes.
• Project administrators manage project permissions for team-managed projects through
custom roles.
• Every company-managed project has a permission scheme.
• A permission scheme grants users, groups, or roles their permissions in your company-
managed projects.
• Like other schemes in Jira, changes you make a to permission scheme update the
permissions for any of the company-managed projects associated with the scheme.
• This makes it easy for Jira admins to manage the permissions of many projects at
once, without having to adjust each project’s settings individually.
• Once a permission scheme is set up, it can be applied to all projects that have the same
type of access requirements.
• Permission schemes set permissions at the project level.

CREATE PERMISSION

• Select > Issues.

• From the sidebar, select Permission Schemes. The Permission Schemes page opens.
• It displays a list of all the permission schemes in your Jira site and the projects that use
each scheme.
• Select Add Permission Scheme. The Add Permission Scheme form appears.
• Give your new scheme a name, and add a short description of the scheme. Descriptions
help you identify schemes in the future.
• Select Add.
TO ADD,USERS,GROUPS AND GRANT PROJECT PERMISSIONS
• Select > Issues.Select Permission Schemes to open the Permission Schemes page,
which displays a list of all permission schemes in your Jira system and the projects that
use each scheme.
• Locate the permission scheme you would like to update, and select Permissions in
the Actions column to view the scheme.
• For each permissions available, select the Edit link to grant the permission to a user,
group, or role. This displays the Grant permission dialog.
• In the Grant permission dialog, select who to grant the permission to and click
the Grant button.

OUTPUT:

RESULT:

Thus the permissions are tested and managed in JIRA.

 EX.NO: 12
SMART QUERIES AND FILTERS IN JIRA

AIM:
To create queries and filters in JIRA.

DESCRIPTION:

QUERIES

• Queries are a series of simple elements strung together to form a more complex
question.
• A query has three basic parts: fields, operators, and values.
• Fields are different types of information in the system. Jira fields include priority,
fixVersion, issue type, etc

CREATING A QUERY

• In the top navigation bar, select Filters.

• Select Advanced issue search.
• Use quick filters for basic search or switch to JQL for advanced search.
• Switch between list and detail view by clicking the Change Views button on the top
right of the screen.

FILTERS IN JIRA

• Filters in Jira are used to sort and segment issues by criteria you set.
• For example, you can use filters to narrow a list of issues down to see only those that
are assigned to you, only those of a certain issue type (story, bug, epic, etc.), only
those assigned a specific priority, only open issues, and more.

CREATING FILTERS IN JIRA

• Creating a filter in Jira starts by conducting a search.

• Click the magnifying glass icon in Jira's left navigation menu.
 • click Advanced search for issues just below the search bar.
• Check your search results to make sure the issues that display are the issues you want
to filter for.
• Then, click the Save as to convert your search criteria into a filter.
• Give your filter a name and click Submit.

EDITING FILTERS IN JIRA

• If you want to share your filters with others, favorite (star) or unfavorite (de-star)
them, or make changes to your filters' names, you can do so from the View all
filters screen.
• click Issues and filters in the left navigation menu, scroll down, and click View all
filters.
• Next, click the three horizontal dots icon next to the filter you want to edit, then
click Edit filter details.
• From this menu, you can also make copies of your filters or delete them if you no
longer need them.

OUTPUT:
RESULT:

Thus the queries and filters are created successfully in JIRA.

 EX.NO: 13
BOARDS IN JIRA

AIM:

To create boards in JIRA.

DESCRIPTION:

BOARD

A board displays issues from one or more projects, giving you a flexible way of viewing,
managing, and reporting on work in progress. There are two types of boards in Jira Software:

• Scrum board — for teams that plan their work in sprints

• Kanban board — for teams that focus on managing and constraining their work-in-
progress

• You can use a board that someone else has created, or create your own.
• A project can have multiple boards, and a combination of Scrum boards and Kanban
boards, if you choose.

ACCESSING A BOARD

• Navigate to your desired board.

• On the Project sidebar, click one of the following, depending on what you need to do:
• Backlog, Active sprints, or Reports.
• Kanban board, Backlog, or Reports.

ON A SCRUM BOARD

Backlog
• The Backlog of a Scrum board shows the issues for your project(s) grouped into a
backlog and sprints.
• In the Scrum backlog, you can create and update issues, drag and drop issues to rank
them, or assign them to sprints, epics, or versions, manage epics, and more. You
would typically use the Scrum backlog when building a backlog of issues, planning a
new version, and planning a sprint.
Active sprints
• The Active sprints of a Scrum board displays the issues that your team is currently
working on.
• You can create and update issues, and drag and drop issues to transition them through
a workflow.

Reports
• Reporting is an activity that you will be doing throughout a project.
• Jira Software has a range of reports that you can use to show information about your
project, versions, epics, sprints, and issues.

ON A KANBAN BOARD

Backlog
• By default, Kanban boards have the Backlog column, where you plan work for your
team. Planning work in a small column becomes difficult as more issues are added in
the column.
• By enabling and using the Kanban backlog, you have a bigger space to create and
rank issues, and select issues for your team to start working on.

Kanban board

• The Kanban board is a board that was created using the "Kanban" preset (see Creating
a board).
• Kanban is based on the continuous delivery of work. Rather than plan iterations, the
flow of work is constantly monitored to ensure that there are always tasks being
worked on. This means that when tasks are completed, new tasks are pulled into
work-in-progress.
• Use the Kanban board if your team focuses on managing and constraining work-in-
progress.

Reports
• Reporting is an activity that you will be doing throughout a project.
• Jira Software has a range of reports that you can use to show information about your
project, versions, epics, sprints, and issues.
OUTPUT:

RESULT:
Thus the board has been created successfully in JIRA.
 EX.NO: 14
RICH TEXT IN JIRA

AIM:
To create a rich text in JIRA.

DESCRIPTION:

RICH TEXT

The rich text editor lets your users choose between two options:

• Text mode, which supports a modified version of wiki markdown.

• Visual mode, which is a What You See Is What You Get (WYSIWYG) editor.
• The rich text editor is available on description fields, comment fields, and all Text field
(multi-line) custom fields that use the wiki renderer.

ENABLE OR DISABLE RICH TEXT

• Rich text editing is enabled by default, but you can disable it as follows:
• From the top navigation bar select Administration > System.

• Go to the User Interface section (in the left-side menu) and select Rich text editor.

• Select the Enable rich text editing for users toggle to enable or disable the editor.
• Currently, the editor doesn't support:
• nested tables
• pasting rich text (plain text is fine) that contains complex formatting
• Third-party macros provided by apps that aren't compatible with Jira 9.1 are displayed
in legacy mode:
• The Macro header is not editable in Visual mode, and content within the macro is
presented in text mode (wiki markup).
• You can check the status of your apps on the Rich text editor configuration page:
OUTPUT:

RESULT:
Thus the rich text has been created successfully in JIRA.
EX.NO: 15
SPRINT PLANNING IN JIRA

AIM:
To study about sprint planning in JIRA.

DESCRIPTION:

SPRINT

• A sprint is a fixed time period in a continuous development cycle where teams

complete work from their product backlog.
• At the end of the sprint, a team will typically have built and implemented a working
product increment.
• Jira Software makes your backlog the center of your sprint planning meeting, so you
can estimate stories, adjust sprint scope, check velocity, and re-prioritize issues in
real-time.

CREATING A SPRINT

• Go to the Backlog of your Scrum project.

• Click the Create Sprint button at the top of the backlog.
• Note that you can create more than one sprint, if you want to plan work several weeks
in advance.

• Fill your sprint with stories from the backlog

• Once you've created your sprint, you'll need to fill it with issues.

• Before you do this, make sure you sit down with your team and discuss what work
you'd like to commit to doing. Ensure you add enough work for everyone in the team.

TO ADD STORIES TO YOUR SPRINTS

• Navigate to the Backlog.

• Drag and drop issues from the Backlog onto your sprint.
 • Note that you can also add an issue to your sprint by editing the issue and updating
the Sprint field.
• Start sprint

• Once you've added issues to your sprint and the team is ready to work, you'll need to
start the sprint.

• The sprint is at the top of the backlog. If you want to start a planned sprint that is
lower down, you'll need to reorder your sprints to move it to the top.

TO START A SPRINT

• Go to the Backlog of your Scrum project.

• Find the sprint that you want to start and click Start Sprint.

• Update the Sprint name and add a Sprint goal if you want to, and select the Start
date and End date for the sprint.
• Monitor your team's progress

• During the sprint, you'll probably want to monitor the team's progress. One way of
doing this is by viewing the Sprint Report.

• Close the sprint.

TO CLOSE A SPRINT

• Navigate to the Active sprints of your Scrum board.

• If necessary, select the sprint you want to complete from the sprint drop-down.

• Note that if you have multiple sprints in the Active sprints of your board, the
'Complete Sprint' button will not appear until you select one of the sprints.

• Click Complete Sprint. All completed issues will move out of Active sprints.
OUTPUT:

RESULT:

Thus the sprint has been created and completed successfully.

 EX.NO: 16
DASHBOARD FOR SPRINTS IN JIRA

AIM:
To study about the dashboards for sprint in JIRA.

DESCRIPTION:

DASHBOARD

• Dashboard is the main display you see when you log in to Jira.
• You can create multiple dashboards from different projects, or multiple dashboards for
one massive overview of all the work you're involved with.
• You can create a personal dashboard and add gadgets to keep track of assignments and
issues you're working on. Dashboards are designed to display gadgets that help you
organize your projects, assignments, and achievements in different charts.
• To view all of your dashboards, choose Dashboards > View all dashboards.

CREATING A DASHBOARD

You can create and customize your own dashboard to display the information you need. Only
Jira admins can customize the system dashboard.

• Choose Dashboards > Create dashboard.

• Name your dashboard and add a description so your team knows when to use
it.
• Fill out the remaining fields and click Save.

JIRA DASHBOARD GADGETS

• Jira dashboard gadgets are blocks that appear on your dashboard and allow you to
dynamically access and interact with information from across your instance.
• In many cases, you can also customize and configure dashboard gadgets to get
precisely what you want making them an extremely powerful tool.
 • There are a number of gadgets built into Jira, but you can also download more using
apps from the Atlassian Marketplace and they unlock a wide range of new
capabilities.
• You can find the “Add gadget” button in the top right of your dashboard.

OUTPUT:

RESULT:

Thus the dashboard for sprint has been created successfully in JIRA.
EX.NO: 17
AUTOMATION TOOLS IN JIRA

AIM:
To study about the automation tools in JIRA.

DESCRIPTION:

AUTOMATION

• Automation empowers you to focus on the work that matters, removing the need to
perform manual, repetitive tasks by allowing your teams to automate their processes
and workflows.
• With our simple rule builder, you can configure powerful automation rules to handle
even the most complex scenarios.

RULES

• Rules allow you to automate actions within your system based on criteria that you set.
• Automation rules are made up of three parts: triggers that kick off the
rule, conditions that refine the rule, and actions that perform tasks in your site.

TRIGGERS

• Every rule starts with a trigger. They kick off the execution of your rules.

• Triggers will listen for events in Jira, such as when an issue is created or when a field
value is changed.

• Triggers can be set to run on a schedule, and can be customized before being applied
to a rule.
CONDITIONS

• Conditions allow you to narrow the scope of your rule.

• They must be met for your rule to continue running. For example, you can set up your
rule to only escalate an issue if it is high priority.

• If a condition fails, the rule will stop running and no actions following the condition
will be performed.

RULE STATUS

The status of a rule can be seen on its details screen.

• ENABLED -The rule is currently active.

• DISABLED-The rule is not currently in use.
• DRAFT-The rule has unpublished changes.

AUDIT LOG

• Each of your rules will have an audit log that you can review to see when the rule was
triggered, the final result of the execution, and any actions that may have been
performed.

• You can view the audit log of an individual rule, project-wide or at a global level.
Reviewing your audit logs is an effective way of debugging your rules.

CREATING A RULE

• We can create a simple rule to automatically add sub-tasks to any new bugs, and even
assign them to a specific user.
OUTPUT:

RESULT:

Thus the automated tools has been created and studied successfully.
 EX.NO: 18
CREATE AUTOMATION RULE IN JIRA

AIM:
To create the automation rule in JIRA.

DESCRIPTION:

AUTOMATION

• Automation empowers you to focus on the work that matters, removing the need to
perform manual, repetitive tasks by allowing your teams to automate their processes
and workflows.
• With our simple rule builder, you can configure powerful automation rules to handle
even the most complex scenarios.

RULES

• Rules allow you to automate actions within your system based on criteria that you set.
• Automation rules are made up of three parts: triggers that kick off the
rule, conditions that refine the rule, and actions that perform tasks in your site.

RULE STATUS

The status of a rule can be seen on its details screen.

• ENABLED -The rule is currently active.

• DISABLED-The rule is not currently in use.
• DRAFT-The rule has unpublished changes.

BUILDING A RULE

• Navigate to your Automation settings and select Create rule in the top-right corner.
• Select the Issue created trigger, and select Save.
• Select New condition, and select the Issue fields condition.
 • Configure the condition as follows:
Set the Field to Issue Type
Set the Condition to equals
Set the Value to compare to Bug
Select Save.
• Select New action, and select the Create sub-tasks action.
• Configure the action as follows:
Add 3 sub-tasks, called Inspect code, Troubleshoot and Resolve.
Select Save.
• Select New action, and select the Assign issue action.
• Select a user to specify the assignee, and select Save.
• Give your rule a name, and select Turn it on.

OUTPUT:

RESULT:

Thus the automation rules has been created successfully in JIRA.

EX.NO: 19
TEST AUTOMATION RULE IN JIRA

AIM:
To create the test automation rule in JIRA.

DESCRIPTION:

AUTOMATION

• Automation empowers you to focus on the work that matters, removing the need to
perform manual, repetitive tasks by allowing your teams to automate their processes
and workflows.
• With our simple rule builder, you can configure powerful automation rules to handle
even the most complex scenarios.

ACTIONS

• Actions are the doers of your rule. They allow you to automate tasks and make
changes within your site.
• They allow you to perform many tasks, such as editing an issue, sending a
notification, or creating sub-tasks.

BRANCHING

• Issues in Jira rarely exist in isolation.

• They often contain sub-tasks, are stories that are part of a larger epic, or are simply
linked to other issues using certain relationships.

• This means that when using automation, actions often need to apply, not only to the
source issue that triggered the rule, but also to any issues that are related to the source
issue.
 • Special conditions and actions are available to create powerful rules that can work
across complex issue relationships.

• For example, checking that all sub-tasks of a parent issue are resolved.

OUTPUT:

RESULT:

Thus the test automation rules has been created successfully.

 EX.NO: 20
SUBSCRIPTIONS IN JIRA

AIM:

To study about the Subscriptions in JIRA.

DESCRIPTION:

SUBSCRIPTIONS

• Jira subscriptions keep you abreast of important issues when they arise.

• A subscription in Jira means it will run a query on a scheduled basis and email the
result to you or a group of people.

• If no issues meet that query, Jira will not send email.

• Subscriptions can be configured on a flexible basis.

• Users can create an infinite number of filters and subscriptions.

• Furthermore, the subscription can be sent frequently and include a group of people
who can not unsubscribe.
• The administrators may never know about the presence of such a huge number of
subscriptions.

Now your administrators can view and manage the filters and subscriptions of all Jira users in
one place.
Key highlights:
• Browse all filters and subscriptions on one dashboard
• Manage the private filters of other users
• Manage and delete subscriptions created by any user
• Change the filter owner
• Find broken filters
• Find potentially duplicate filters
• Search for filters by a piece of JQL-query
• Browse agile boards based on a particular filter
• Check if a filter was added to favorites by any of the active users.

OUTPUT:

RESULT:

Thus the subscriptions have been created in JIRA.

EX.NO: 21
VISUAL DASHBOARD ALERTS IN JIRA

AIM:

To create and study about the visual board alerts in JIRA.

DESCRIPTIONS:

VISUAL DASHBOARD ALERTS

• Conceptboard has taken visual communication and visual project management a step
further by introducing visual alerts.

• Now, Conceptboard alerts add important visual context to your conversations by

including a snapshot of the area around the alert so you can stay in the loop wherever
you are.

TASK ASSIGNMENTS IN CONCEPTBOARD

• It’s easy to centralize all your discussions on visual content in Conceptboard, but now
we’ve made it even easier to take action, with task assignments.
• All comments can be marked as a task, but you can assign tasks to teammates, simply
by @mentioning a team member in a comment box and marking the comment as a
task.
• Your teammates will get a visual alert in their email and home page feed, adding
important visual context to the task assignment, and can see a list of all their tasks in
the board and on the home page.
• To get the attention of your teammates on important tasks, @mention them directly in
a comment.
• They’ll receive an email and home feed notification that includes the comment and
a visual preview of the comment area.
• You can mention anyone that is in your contact list.
OUTPUT:
RESULT:

Thus the visual dashboard alerts is created successfully in JIRA.

EX.NO: 22
PRODUCT ROADMAPS IN JIRA

AIM:

To study about the product roadmaps in JIRA.

DESCRIPTION:

ROADMAP

• A product roadmap is a shared source of truth that outlines the vision, direction,
priorities, and progress of a product over time.
• It’s a plan of action that aligns the organization around short and long-term goals for
the product or project, and how they will be achieved.
• While it's common for the roadmap to show what you’re building, it’s just as
important to show why.
• Items on the roadmap should be clearly linked to your product strategy, and your
roadmap should be responsive to changes in customer feedback and the competitive
landscape.
• Product owners use roadmaps to collaborate with their teams and build consensus on
how a product will grow and shift over time.
• Agile teams turn to the roadmap to keep everyone on the same page and gain context
for their everyday work and future direction.

INTERNAL ROADMAP FOR DEVELOPMENT TEAM

• These roadmaps can be created in several ways, depending on how your team likes to
work. Some common versions include the detail about the prioritized customer value
to be delivered, target release dates and milestones.
• Since many development teams use agile methodologies, these roadmaps are often
organized by sprints and show specific pieces of work and problem areas plotted on a
timeline.

INTERNAL ROADMAP FOR EXECUTIVES

• These roadmaps emphasize how teams' work supports high-level company goals and
metrics.
• They are often organized by month or by quarter to show progress over time towards
these goals, and generally include less detail about detailed development stories and
tasks.
 BEST PRACTICES FOR BEST ROADMAP

Building and maintaining product roadmaps is an ongoing process to embark upon with your
team. There are a few simple ways to set yourself up for success:

• Only include as much detail as necessary for your audience

• Keep the roadmap evenly focused on short-term tactics and how these relate to long-term
goals
• Review roadmaps on a regular basis and make adjustments when plans change
• Make sure everyone has access to the roadmap (and checks it on a regular basis)
• Stay connected with stakeholders at all levels to ensure alignment

OUTPUT:
RESULT:

Thus the roadmap for the product has been created successfully in JIRA.
EX.NO: 23
INFORMATION RADIATORS IN JIRA

AIM:
To study about the information radiators in JIRA.

DESCRIPTION:

INFORMATION RADIATORS

• An information radiator is an electronic board or a physical board that provides useful

summarized and properly laid out information about a team's progress.
• This is extremely important for the stakeholders to view and typically if you walk into
a development team's area, or even that part of the building where they are working,
or anywhere else, if these information radiators are present, that enhances
transparency about the team's progress, so let's go ahead and create an information
radiator dashboard.

AGILE WALLBOARD

• This gadget displays the team task board and is a beautiful way of highlighting the
flow of work.

• You can see items from the current sprint together with their status and assignee,
giving you an overall picture of the sprint contents.

• It’s a really useful gadget to look at during your daily stand-up, as you can point to
specific tasks during the meeting.

PIE CHART

• It helps you to know exactly how much work each team member has and how quickly
they are able to complete it.

• As pie charts offer a very visual and immediate picture of what’s going on, this gadget
is a great choice for Jira Wallboards.

• You can also use it during meetings; hovering the mouse over a piece of the pie gives
you the issues as a percentage and clicking on a segment takes you to those issues for
further detail.
DAYS REMAINING IN SPRINT

• This simple gadget does exactly what it says on the tin; it gives you how many
working days you have before the next release is due in a particular sprint.

• It’s uniquely suited to wallboards because a quick glance gives passers-by the
information they need to stay on track.

AGILE SPRINT HEALTH

• The Agile Sprint Health gadget displays a color-coded bar graph that lets you see a
concise visual summary of the issues in a specified sprint.

• It shows your overall progress based on the time elapsed, work completed, and work
remaining.

• The blue, yellow and green colors represent different issues in different statuses.
Usually, blue is “To Do”, yellow is “In Progress” and green is “Done”. During
meetings you can click any part of the bar to view the issues in the corresponding
statuses.

• The work completed percentage is based on the estimation statistic used for your
board.

SPRINT BURNDOWN

• This gadget displays a series of line graphs showing the burndown for a particular
sprint.

• The grey line is the ‘guideline’ based on the total estimated issues at the start of the
sprint and the red ‘remaining values’ line is the actual work done .

• The sprint burndown is a popular gadget that lets passers-by see how the team is
performing and whether the sprint is on track or not.
OUTPUT:
RESULT:

Thus the information radiators has been created successfully in JIRA.

 EX.NO: 24
CLOSE A SPRINT IN JIRA

AIM:
To close the sprint in JIRA.

DESCRIPTION:

CLOSING A SPRINT

• The end of a sprint is the time where your team takes stock of its progress.
• This usually includes demonstrations of the work completed during the sprint,
followed by a sprint retrospective to analyze where improvements can be made.

• As the team lead, Scrum master, or product owner, you can also use this time to check
how your team is progressing against the overall version, and provide feedback to your
stakeholders.

BEFORE YOU BEGIN

• Sprints only apply to Scrum boards.

• If you are using a Kanban board, check out Deploying a release instead.
• To complete a sprint, you must be a Jira Administrator or a user with the Manage Sprints
permission.
If you can't complete a sprint, your board's filter may be complex, and Jira Software is unable
to determine which projects will be returned by the query.
See Using Manage Sprints permission for advanced cases if you need help.

COMPLETING THE ACTIVE SPRINT

• Go to the Active sprints of your Scrum board.

• If necessary, select the sprint you want to complete from the sprint drop-down.
• Note that if you have multiple sprints in the Active sprints of your board, the
'Complete Sprint' button will not appear until you select one of the sprints.
• Click Complete Sprint.
• All completed issues will move out of Active sprints.
 • If the sprint has incomplete issues, select from one of the following:
• Backlog, to move the issues to the backlog
• Any future sprint, to move the issues to any future sprint that's already created
• New sprint, to create a new sprint and then move the issues to the new sprint

• Note that your issues won't be marked with the date the sprint was closed; however,
you can always view the sprint for an issue to find out when the sprint ended.
• If you have parent issues that are 'Done' but sub-tasks that are not 'Done', you won't be
able to end the sprint.
• You must complete the sub-tasks first.
• If you have parent issues that are not 'Done' but have sub-tasks that are all 'Done', the
parent issues will still be moved to the selected future sprint or to the Backlog.
• If these parent issues are part of another active sprint, the previously completed sub-
tasks are still 'Done'.

OUTPUT:

Before closing the sprint:

After closing the sprint:

RESULT:

Thus the sprint has been closed successfully in JIRA.

EX.NO: 25
REPORTS IN JIRA

AIM:

To create a report in JIRA.

DESCRIPTION:

REPORTS

• One part of ensuring the success and smooth operations of your projects in JIRA is
reporting.
• It involves gaining the knowledge about the health, progress and overall status of your
JIRA projects through Gadgets, report pages or even third party applications.

• The goal of this guide is to provide an overview of the tools available to JIRA users
today and how they can be used to fulfill the different types of reporting needs that
users face today.

TOOLS FOR REPORTING

STANDARD REPORTING
• JIRA offers reporting in a number of different formats.
• Project reports that are available from the home screen of the selected project, Gadgets
that can be added and arranged in Dashboards and for each filter, the issue navigator
offers various output formats that can be used in third party reporting software.
• Additionally, we will mention some advanced methods that customers have been
using.
• In JIRA, a project will automatically offer standard reports available to the user
without any necessary configuration.
• These standard reports comprise a wide range of reporting applications such as time
tracking, workload and also abstract reports like Pie Charts that can be used in various
ways.
Standard Report Description

Average Age Report Shows the average age (in days) of unresolved issues.

Created vs Resolved Shows the number of issues created vs number of issues resolved
Issues Report over a given period of time.

Pie Chart Report Shows the search results from a specified issue filter (or project)
in a pie-chart, based on a statistic of your choice.

Recently Created Shows the rate at which issues are being created.
Issues Report

Resolution Time Shows the average time taken to resolve issues.

Report

Single Level Group Shows the search results from an issue filter, grouped by a field
By Report of your choice.

Time Since Issues Shows the number of issues for which your chosen date field
Report (e.g. 'Created') was set on a given date.

User Workload Report Shows how much work a user has been allocated, and how long
it should take.

Version Time Shows progress towards completing a given version, based on

Tracking Report issues' work logs and time estimates.

Version Workload Shows how much outstanding work there is (per user and per
Report issue) before a given version is complete.
Reporting Gadget Description
for JIRA Data

Activity Stream The Activity Stream Gadget displays a summary of your recent
activity.

Administration The Administration Gadget displays quick links to administrative

functions.

Assigned to Me The Assigned To Me Gadget displays all open issues in all projects
assigned to the current user viewing the dashboard.

Average Age The Average Age Gadget displays a bar chart showing the average
number of days that issues have been unresolved.

Bugzilla ID Search The Bugzilla ID Search Gadget allows the user to search all JIRA
issues for references to Bugzilla IDs.

Calendar Displays issues and versions in calendar format, based on due date.

Created versus Displays a list of all the issue filters that you have marked as
Resolved Issues favourite.

Favourite Filters The Favourite Filters Gadget displays a list of all the issue filters
that have currently been added by you as a favourite filter.

Filter Results The Filter Results Gadget displays the results of a specified issue
filter.

Heat Map Displays the relative weighting of the values in a given field, for
issues returned from a given project or filter.

Issues in Progress Displays all issues that the current user is working on.

Introduction The Introduction Gadget displays a configurable introduction

message on the dashboard.
Issue Statistics The Issue Statistics Gadget displays the collection of issues returned
from a specified filter, broken down by a specified field.

Labels Displays a list of all the labels in a specified project.

Pie Chart The Pie Chart Gadget displays issues from a project or issue filter,
grouped by a statistic type, in pie-chart format. The issues can be
grouped by any statistic type (e.g. Status, Priority, Assignee, etc).

Projects The Projects Gadget provides information and various filters related
to a specified project(s).

Quick Links The Quick Links Gadget displays a number of useful links to issues
associated with the current user.

Recently Created The Recently Created Issues Gadget displays a bar chart showing
Issues the rate at which issues are being created, as well as how many of
those created issues are resolved.

Resolution Time The Resolution Time Gadget displays a bar chart showing the
average resolution time (in days) of resolved issues.

Road Map The Road Map Gadget shows versions which are due for release
within a specified period of time, and a summary of progress made
towards completing the issues in those versions.

Text Displays a configurable HTML message.

Time Since Chart Displays a bar chart showing the number of issues that something
has happened to within a given time period. The 'something has
happened' is based on a date field that you choose, such as 'Created',
'Updated', 'Due' or 'Resolved'.

Two-Dimensional Displays statistical data based on a specified filter in a configurable

Filter Statistics table.

Voted Issues Displays issues for which the current user has voted.
OUTPUT:

RESULT:

Thus the report is created and executed successfully in JIRA.

EX.NO: 26
SPRINT RETROSPECTIVE ITEMS IN JIRA

AIM:
To study about the sprint retrospective items in JIRA.

DESCRIPTION:

RETROSPECTIVE IN JIRA

• Agile retrospectives might be regarded as overhead, or considered as “Post-Mortem”

meetings, but these are held only when the project is concluded (not during the
lifetime of the project).

• Agile coaches around the world will agree on the fact that the retrospective is the key
to your products incremental value. And most of all, it’s key for your team’s
continuous improvement in the long term.

• Without a retrospective at the end of every sprint, Agile wouldn’t be the same. Issues
wouldn’t be fixed before you can prevent them from snowballing into proportions
difficult to manage.

• And you definitely would be missing out on the long-term benefits of Agile.

5 STAGES OF RETROSPECTIVES
• Set the Stage

• Gather Data

• Generate Insights

• Decide what to do

• Close the retrospective

Set the Stage in Jira

• A retrospective is a place for everyone on the team to share. Setting the stage involves
creating that “safe space”.

• Everything from the venue, to the TRUST needed for people to freely share.

• JIRA is the perfect “Venue” to host your retrospectives since you already have all of
the sprint information there.

• So it’s easy to follow up and to have in consideration for future sprints. Just choose
your preferred conference software and have the entire team connected and with their
camera on.

Gather Data

• During an in-house team Agile Retrospective session using a whiteboard where the
team takes turns to input ideas, these give way for “Groupthink”.

• Groupthink is that phenomenon, where the first person brings up an issue, the whole
team seems to agree or nod and any future comments on that issue will be withheld.
This is not ideal since you want to know everyone’s perspective on a given issue.

• It’s a much better approach to have every team member input ideas separately,
without fear of judgement or bias.

Generate insights

• At this stage, we filter all of the topics to see which ones the team value the most. As
well as decide on which topics we are going to work on first.

• You can also customize the voting preferences to limit the number of votes per player
and topics.

• This is a great way to prioritize and filter the ideas worth your while.

Decide what to do

• This is the most important stage. It is also the most overlooked.

• Your retrospective session is of no value if your result is a complaint or a very broad

statement like “QA needs to improve”.

• The result should be a team agreement about what to do about the issue.
 • It should be expressed as an ACTION ITEM. This is the Most Valuable Output from
your Retrospectives.

• But it’s also worthless if you don’t follow up on it. And, as we all know, that happens far
too often. That’s why an action item should take the shape of a Jira task or an item on
your checklist.

Close the retrospective

• Closing the retrospectives can be a formal agreement. Or it can be a very casual nod
from the team members agreeing about the resulting action items.

• Afterwords, the entire team agrees on who to assign as an action item owner.

• The person assigned is not who’s performing the task. It should be who’s in charge of
making it happen. Again, this is easy to do using Jira.

OUTPUT:

RESULT:

Thus the retrospective is created successfully in JIRA.

EX.NO: 27
PLANNING POKER IN JIRA , PART 1

AIM:
To plan poker using planning poker app in JIRA

DESCRIPTION:

PLANNING POKER:
Planning poker, also known as “scrum poker” and “pointing poker”, is a gamified technique
that development teams use to guess the effort of project management tasks. These
estimations are based on the entire group’s input and consensus, making them more
engaging and accurate than other methods.

BENEFITS:

• It helps to estimate from planning poker are statistically higher than

individual ones.
• It was also noted that for the same tasks, planning poker estimates were
more accurate than individual ones.
• It helps in estimating tasks relative to each other.
• Identifying gaps in requirement and implementation.

PROCEDURE:

Step1 – Go to your JIRA instance and click Applications at the top right under your user
management dropdown.
Step 2 – Click Application Links in the left side sub navigation section on the page.

Step 3 – Type the Application URL from your PlanningPoker integration settings and
click Create new link.

Step 4 – Click Continue in the modal. If it says there is no response do not worry and
continue with the integration.
Step 5 – Type the Application Name and select the Application Type. Both can be found in
your integration settings on PlanningPoker. Do not enter any of the other variables on this
screen.

Step 6 – Edit the new application Link by clicking the pencil icon.
Step 7 – Click Incoming Authentication

Step 8 – Add your integration details from PlanningPoker in to the corresponding fields in
the modal. Remember to scroll down in the modal to get to all the fields.
Step 9 – Save the settings at the bottom of the modal window.

RESULT:

Thus Planning poker integration on JIRA executed successfully.

EX.NO: 28
PLANNING POKER IN JIRA , PART 2

AIM:
To plan poker using planning poker app in JIRA

DESCRIPTION:

PLANNING POKER:
Planning poker, also known as “scrum poker” and “pointing poker”, is a gamified technique
that development teams use to guess the effort of project management tasks. These
estimations are based on the entire group’s input and consensus, making them more
engaging and accurate than other methods.

Estimation can be improved by using planning poker apps. Over time, theseapplications
will refine estimates and make planning more accurate.

PROCEDURE:

Step 1 – Type your Host Name and press Link on the PlanningPoker integration page.

Step 2 – Press Authorize PlanningPoker and then Allow in the window that then pops up.
Step 3 - Create a new game you will now be able to pull stories directly in from
JIRA and even allow the points from your planning sessions to sync back
automatically.

IMPORTING STORIES:

Step 1 – From the Dashboard: Click Create Game.

Step 2 – After you enter your game details scroll down to the Enter Stories section.

Step 3 – Click Integrations.

Step 4- Select a System & Domain.

Step 5 – Then Select your Project, Sprint and What to Sync back to JIRA.

Step 6 – Review/Edit your Stories.

Step 7 – Either Save or Start your game.

RESULT:
Thus Planning poker on JIRA executed successfully.