You are on page 1of 6

JIRA 7 Quick Start (MASTERING)

------------------------------

Jira integrates with Git. (Explore)

The main features of Jira for agile are:


- Iterations Planner
- Iteration Reporter
- Bug Tracker (resolve issues, by creating tasks, assign them to users)
- Project management system with end-to-end traceability.

JIRA Software: JIRA Core + JIRA Agile

various applications of JIRA:


- Bug tracking
- Change requests
- Helpdesk tickets
- Project management
- Test case management
- Requirements management
- Process management

Customer makes a Request/Incident report ==> creates a ticket.

Each ticket has a progress STATUS and is updated with ANNOTATIONS and ATTACHMENTS
(Public/Private).

Customers are notified of progress made on their ticket until it is complete.

JIRA comes with 4 standard Issue Types: (Bug, Epic, Story, and Task)
- Bug
- Improvement
- New Feature
- Task (+Sub-task)

Test campaign: Collection of individual test cases

Workflow for a test case: Open, WIP, Blocked, Passed, Failed, Closed, Re-opened

Issue Navigator : Searching Issues Primarily.


Issues can be Edited, Moved, Transitioned, Deleted, Watched, Stop watching.

JQL : lets you search the issues efficiently

REPORTS:
----------
Reports help management take wise decisions at the right time. lot of built-in
project reports.

When you open any project page, the default view is the summary view, which
contains an Activity Stream that shows whatever is happening in the project, such
as the creation of new issues, status updates, comments, and, basically, any change
in the project.

a link for Reports (in sidebar)


Agile reports:
1. BurnDown Charts (Track total work remaining. Project likelihood of achieving the
Sprint Goal)
2. Sprint Report (monitor if team is overcommitting)
3. Velocity chart (Estimate the work, team can realistically achieve in future
sprints)
4. cumulative flow diagram (Id potential bottlenecks)
5. Version report (whether version will release on time)
6. Epic Report (track remaing INCOMPLETE work)
7. Epic Burndown (whether Epic will release on time)
8. Release Burndown (whether version will release on time)

Also available are


- Issue analysis Reports(7)
- Forecast Reports(3)

User Workload Report:


can tell us about the occupancy of various resources in all the projects. helps in
distributing the tasks among users.

JIRA FOR TEST MANAGEMENT:


--------------------------------

Test management is the software process of performing tests to verify the


requirements.

Test campaigns are a collection of test cases. A test campaign can be created to
collect all the test cases of a particular module in your project.

In any issue-tracking system, the issues will be created, then moved to the In
Progress state, and finally Closed. This is the scenario of a simple workflow with
three states: Open, In Progress, and Closed, which would only work in ideal cases,
but in real-world cases, the workflows, that is, how the issue will move from one
state to another, could be quite complex. ==> Customizing the workflow

For instance, sometimes you need to wait for some information from the client to
act further on the issue; there could be a case when someone will review your task
before closing.

Go to: Administration | Issues | Statuses (under Issue Attributes) and click on the
Add status button

Go to Administration | Issues | Workflows (under Workflows) and copy the default


JIRA workflow

Save and open workflow in the Text tab

Remove unwanted transitions, Adding new steps can be done.

You can also Limit the project visibility to certain groups and individuals

Zephyr paid add-on: full-fledged test management in JIRA

IMPLEMENTATION OF USE CASES:


----------------------------------
1. Gathering requirements:

If you already have a Confluence instance running, you can use it to create
configuration documents, which can be accessed by all the stakeholders. Usually,
people use Confluence along with JIRA to collaborate on documents and share
information.

- What kind of issue tracking? track bugs in your ongoing project


- Issue types required: If JIRA is going to be used for simple bug tracking, then
the existing issue types are sufficient.
- Issue workflow: How your issue will move from one state to another

WORKING WITH AGILE BOARDS:


-------------------------------
2 Agile methodologies called Scrum and Kanban in JIRA for Agile tracking.

JIRA Software: provides great features for implementing Agile techniques

Scrum boards:
- The Scrum technique focuses on breaking up the requirements into small doable
tasks.
- Then, a prioritized list of these tasks is created (called a sprint), which can
be performed in 1-4 weeks.
- The objective of sprint is to create a deliverable feature or product and not
just a prototype.
- More sprints can be created to complete the whole requirement and finish the
product or project.
- The tasks that are yet to be done are kept in a list called a backlog.

Boards | View All Boards | Create board | Create a Scrum/Kanban board with sample
data

Populating, ranking, and estimating a backlog using story points:

In the new scrumboard we will see list of issues that are "pending" in the backlog
window and a sample sprint.

Backlog contains issues that are pending in the project. These issues are yet to be
planned for execution.

As soon as the sprint has started, you manage and work on it using the "Active
sprints tab".

NOTE: Sprint is a time period during which specific planned activities need to be
finished. The Scrum master or the project manager can define the order in which
issues need to be completed. This order is also known as rank, and the team who is
working on these issues needs to follow this order. The rank is important because
there are certain tasks that need to be completed before other tasks can be
started.

In a Scrum methodology, the estimation of individual tasks is not only done on the
basis of the amount of time spent, but also on the complexity of the tasks. For
instance, there are two tasks whose time estimate is one day, but the first task is
complex to execute, for example if it is the first time that the task has been
executed by the team. The complexity is measured by story points. The story point
can be any number between 1 to 10 or any number in the Fibonacci sequence, that is,
1, 1, 2, 3, 5, 8, 13, 21. The higher the number, the more complex the task.

A Scrum master can assign story points to the issues in the sprint, although it's
not mandatory to have story points with each issue in the sprint. However, having
them will give the team an idea about the complexity of the issue.

JIRA Software allows you to create another sprint even if the active sprint is not
complete; however, the new sprint cannot be started.

1.in the Backlog tab click on the Create Sprint button


2.An empty sprint will be created.
3.start dragging your issues from Backlog to your sample sprint
4.you may reorder them within the sprint and define their rank
5.Optionally, you can also create epics to group multiple stories together. Epic is
nothing but a large story.
6. finally, drag issues from your sprint to the epic. This will assign issues to be
part of these epics:
7. you can start the sprint. Click on the Start Sprint link

The moment you start the sprint, you will be taken to the Active sprints tab in the
Scrum board. Here, you will see a list of all the issues in your sprints across
three columns, that is,

To Do || In Progress || Done:
|| ||
|| ||

issues are grouped using a swimlane.

Cards are also available: Mastering JIRA- Ref page 266.

Now, the moment the sprint starts, a baseline is formed between the start date and
the end date in BURNDOWN CHART. When the issue is resolved, its story points are
burned and the total remaining story points of the whole sprint decreases.

When the team starts working on the issues, another line of red color starts
following the baseline. Looking at this chart, the whole team can easily figure out
if they are on track or off track. If the line for Remaining Values is progressing
above the baseline Guideline, then it shows that the story points are being burned
slowly.

It's clear by looking at this Burndown chart that by the end of the sprint, not all
story points were burned; these unfinished issues will be added back to the backlog
when the sprint is completed.

A Kanban board doesn't have any Plan mode like the Scrum board. It only has the
Work mode,

JIRA WITH BITBUCKET AND GITHUB:


-----------------------------------
JIRA comes with a built-in functionality to connect with the Bitbucket and GitHub
repositories.

Once the repositories are listed in the instance, the Git commit messages can
include the JIRA issues ID, and these files will be displayed under the JIRA view
issue Source tab.
JIRA WITH CONFLUENCE
------------------------

Confluence, is used widely for online collaborations. Users can use it to prepare
documentation, tutorials, articles, blogs, project reports and various other types
of documents. Integrating JIRA with Confluence allows users to CREATE REAL-TIME
JIRA reports in Confluence.

Networked Help Desk API :


Several different applications can synchronize data in one uniquely identified
shared ticket.

"Zendesk Support" is a system for tracking, prioritizing, and solving customer


support tickets. It puts all customer information in one place so that everything
is in a single location.

"Zendesk Connect" is CUSTOMER INTELLIGENCE SOFTWARE built for targeted campaigns


and proactive engagement.