Scribd
Upload
81 views19 pages

Jira

Uploaded by

Aniket Shinde
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
81 views19 pages

Jira

Uploaded by

Aniket Shinde
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 19

Jira: Empowering Developers

A bit of History
• The word Jira is derived from the Japanese word ‘Gojira’ which means ‘Godzilla’.
• It has been developed since 2002.
• At first JIRA was purely an issue tracker.
• But later it was split into 2 packages:-
1. Jira software:- Base software including project management, issue tracking and Jira work management.
2. Jira service Management:- helps with customers service management.
What is Jira?
• Jira is a tool developed by an Australian company named
“Atlassian”.
• Jira is an issue tracking product and It provides bug tracking,
issue tracking, and project management functions.

Photos provided by Unsplash


JIRA Uses.
 Bugs Tracking
 Issue tracking
 Help-desk/Support/Customer Service
 Project Management
 Meeting schedular
 Task Tracking
 Requirements Management
 Workflow/Process Management
JIRA Key concepts.
1. Issues
2. Projects.
3. Workflow.

Photos provided by Unsplash


What is an issue?
• A task, a bug, a feature request.
• Core Jira applications.

Photos provided by Unsplash


7

Relationship between issues.


• Parent and child relationship.
• A parent issue is an issue that sits above another issue.
• A child issue is an issue that sits below another issue
• or example, if you have this issue hierarchy:
• For example,
Epic
Story, Task, Bug
Subtask

NEXT
Types of issues?

By default, software projects come with one parent issue type:


1. Epic
By default, software projects come with three standard issue
types:
1. Bug
2. Story
3. Task
By default, software projects come with one child issue type:
1. Sub-task
9

Hierarchy levels of issue.


Jira have three levels of hierarchy.
•Epic issues, which represent high-level initiatives or bigger pieces of work in Jira.
•Standard issues represent regular business tasks.
•Subtask issues, which can help your team break a standard issue into smaller chunks

NEXT
10

Issue Priorities.
• An issue's priority indicates its relative importance.
• Can be customizable.
• The default priorities are listed below.

Highest-Highest priority. This problem will block progress.


High- Indicates that this issue is causing a problem and requires urgent attention.
Medium- Indicates that this issue has a significant impact.
Low-Indicates that this issue has a relatively minor impact.
Lowest-Lowest priority

NEXT
11

Workflow
• Process from creation to completion.
• Jira workflows are composed of 3 unique elements:
1. Status: issue is within the workflow. Open, In Progress, In Review,
Scheduled, Pending, Waiting, etc.
2. Transition: Action being taken to move an issue from status to
status.
3. Resolution: Indicate the outcome of an issue, such as Fixed, Won't
Fix, Duplicate, Closed, Resolved, Shipped, Completed, Done,
Finalized, Won’t Do, etc.

NEXT
12

NEXT
13

What is Projects?
A JIRA project is a collection of issues, and is defined according to your
organization's requirements. For example, a JIRA project could be:
• A software development.
• A project marketing campaign.
• A helpdesk system
• A leave request management system.
• A website enhancement request system.

NEXT
14

Components
• Smaller chunks of projects.
• Grouping issues into specific areas of work.
• It is also used to filter and categorize issues

NEXT
15

What is a version?
• For some types of projects, particularly software development, it is useful to be able to associate an issue with a
particular project version (e.g. 1.0 beta, 1.0, 1.2. 2.0).

• Issues have two fields that relate to versions :

1. Affects Version(s) -- this is the version(s) in which the issue is manifesting. For instance, a software bug
might affect versions 1.1 and 1.2.

2. Fix Version(s) - this is the version(s) in which the issue was (or will be) fixed. For instance. the bug affecting
versions 1.1 and 1.2 might be fixed in version 2.0. Note that issues which do not have a Fix Version are
classified as 'Unscheduled, as shown in the screenshot above
NEXT
16

Advantages of having Jira


• Streamlined Project Management: Offers robust tools for planning, tracking, and managing projects efficiently.

• Customizable Workflows: Adaptable workflows that can be tailored to fit any team's unique processes.
For Marketing Team:
Default Workflow: To Do → In Progress → Done.
Custom Workflow: Planning → Design → Content Creation → Approval → Published.

• Scalability: Scales easily from small teams to large enterprises, supporting growth and changing needs.

• Integration Capabilities: Integrates seamlessly with numerous third-party tools, enhancing overall productivity.

• User-Friendly Interface: Intuitive and easy-to-navigate interface that reduces the learning curve for new users.

NEXT
17

Drawbacks of Jira
These disadvantages are based on common user feedback and industry analysis regarding Jira's performance, cost,
complexity, and integration challenges. These issues are frequently highlighted in reviews and feedbacks.

• Complexity: Jira can be complex to set up and configure, requiring a steep learning curve for new users.
• Cost: The pricing model can become expensive, especially for large teams and organizations.
• Performance Issues: As the number of users and projects increase, Jira may experience performance
slowdowns.
• Customization: Over-customization can lead to maintenance challenges and complicate upgrades.
• Integration: Integrating Jira with other tools can be cumbersome and sometimes requires additional plugins
or custom development.
NEXT
18

Competitors

User-friendly interface, Versatile project management Integration with Microsoft Highly customizable workflows, automation
intuitive Kanban boards, ease with goal tracking, ecosystem, comprehensive DevOps features, suitable for various project
of use for small teams. affordability, and extensive tools like CI/CD pipelines, version management needs.
features in one platform. control.

Comprehensive task and Advanced project planning with Gantt


project management, task charts, real-time updates, strong
dependencies, collaboration collaboration tools.
tools for large teams.
NEXT
19

Key Users and Audience of Jira.


• According to a 2014 survey conducted by Atlassian, approximately one-third of respondents said they now also use JIRA
for non-software development projects such as HR, finance or marketing. While the basic principles of great collaboration
run across every team, functional teams have distinct needs when they need to get things done faster, more efficiently, and
with fewer headaches.

 Software Development Teams: Developers, engineers, and technical staff


 Project Managers: Professionals responsible for planning, executing, and monitoring projects.
 Agile Teams: Scrum masters and product owners who follow agile methodologies for project management.
 IT Departments: IT service management, incident management, and support ticket tracking.
 Business Stakeholders: Managers and executives who need visibility into project progress, metrics, and reports.
 Quality Assurance Teams: Testers and QA engineers who manage testing activities and track issues.
 Service Desk Teams: Support agents who handle customer inquiries, incidents, and service requests.

NEXT

You might also like