Jira Basic Concepts: Overview

Jira is a powerful project management and issue tracking tool developed by Atlassian, widely
used for software development, IT service management, and general project tracking. It helps
teams plan, track, and manage work efficiently.

1. Key Jira Concepts

 Issue:
The fundamental unit of work in Jira. An issue can represent a bug, user story, task, epic,
or any work item. Issues are tracked from creation to completion.

 Project:
A container that organizes a collection of related issues. Projects can represent software
products, business initiatives, or any team’s work. Each project has its own workflows,
permissions, and configurations.

 Board:
A visual representation of work items (issues) that helps teams track progress. Jira
supports Agile boards such as Scrum and Kanban, where issues move across columns
representing workflow statuses.

 Workflow:
Defines the lifecycle of an issue, including statuses (e.g., To Do, In Progress, Done) and
transitions (actions that move issues between statuses). Workflows can be customized
to fit team processes.

2. Jira Issue Types

Common issue types include:

 Epic: Large feature or goal spanning multiple issues.

 Story: User-centric feature or requirement.

 Task: General work item.

 Bug: Defect or problem to fix.

 Sub-task: Smaller piece of work under a parent issue.

3. Project Types

 Team-managed Projects:
Designed for teams needing simplified, independent configuration and control over their
own processes.

 Company-managed Projects:
Managed by Jira administrators with standardized configurations across multiple teams
and projects, offering advanced features.

4. Agile Boards

 Scrum Board:
Supports sprint planning and iterative delivery. Focuses on fixed-length sprints and
backlog management.

 Kanban Board:
Supports continuous flow of work, visualizes work-in-progress limits, and optimizes cycle
time.

5. Additional Features

 Timeline View: Plan and track work over time, visualize dependencies.

 Insights and Reporting: Built-in reports to track velocity, burndown, and team progress.

 Integrations: Over 6000 apps and plugins extend Jira’s capabilities.

6. Working with Jira

 Create issues to represent work items.

 Assign and prioritize issues.

 Transition issues through workflows to reflect progress.

 Collaborate using comments, attachments, and notifications.

 Use filters and dashboards to monitor and report on work.

Summary Table
 Concept Description

Issue Unit of work (bug, task, story, epic, sub-task)

Project Container organizing related issues

Board Visual workflow representation (Scrum/Kanban)

Workflow Defines issue lifecycle statuses and transitions

Issue
Epic, Story, Task, Bug, Sub-task
Types

Project Team-managed (simple), Company-managed

Types (advanced)

Jira Issue Types

Jira Issue Types Overview

Jira issues represent units of work and come in various types to suit different project needs.
Each issue type can have its own workflow, fields, and properties.

Default Jira Issue Types

 Epic:
A large body of work that can be broken down into smaller issues such as stories, tasks,
or bugs. Epics represent significant features or goals spanning multiple sprints or
releases.

 Story:
A user-centric requirement or feature, typically deliverable within a sprint. Stories are
often linked to epics.

 Task:
A generic piece of work that needs to be completed. Tasks can be technical or non-
technical and are siblings to stories and bugs.

 Bug:
Represents a defect or problem that needs fixing. Like stories and tasks, bugs are
standard issue types.

 Sub-task:
A smaller, actionable piece of a larger issue (story, task, or bug). Sub-tasks cannot have
children and always belong to a parent issue.

Jira Issue Type Hierarchy Levels

Jira organizes issue types into a hierarchy to manage work from large goals to granular tasks:
 Hierarchy Level Issue Types Included Description

Level 2+
Strategic or portfolio-level issues
(Optional, Initiative, Capability, Feature
above Epics (available with Advanced
Premium/Enterpri (custom types)
Roadmaps)
se)
Large bodies of work that encompass
Level 1 Epic
multiple standard issues

Standard issues representing user

Level 0 Story, Task, Bug
stories, generic tasks, or defects

Smaller units of work that break

Level -1 Sub-task
down standard issues

Key Points About Hierarchy and Relationships

 Epics are parents to Stories, Tasks, and Bugs via the Epic Link field.

 Stories, Tasks, and Bugs are siblings on the same hierarchy level and cannot be parents
or children of each other by default.

 Sub-tasks are children of Stories, Tasks, or Bugs and cannot have their own children.

 With Jira Premium or Enterprise, you can add custom hierarchy levels above Epics (e.g.,
Initiatives) to better fit complex project structures.

 Jira does not allow creating hierarchy levels below Sub-tasks.

 Custom issue types can be created and assigned to any hierarchy level as needed.

 Each issue type can have its own workflow, screens, and fields, enabling tailored
processes.

Example of Typical Jira Issue Hierarchy

Jira organizes issue types into a hierarchy, allowing teams to manage work from strategic goals
to granular tasks. Here's a typical hierarchy:

1. Initiative: the highest level (customizable) representing organizational goals or themes.

2. Epic: a major deliverable or large body of work.

3. Story/Task: individual pieces of work contributing to the Epic.

4. Sub-task: specific actions needed to complete a Story or Task.

Example:

 Initiative: Improve User Onboarding Experience

o Epic: Redesign Registration Flow

 Story: Implement Multi-step Form

 Sub-task: Design wireframes

 Sub-task: Develop front-end

Additional Jira Issue Components

  Summary: Short title describing the issue.

 Description: Detailed info about the issue.

 Status: Current workflow stage (e.g., To Do, In Progress, Done).

 Assignee: Person responsible for the issue.

 Reporter: Person who created the issue.

 Priority: Urgency level (Low, Medium, High).

 Linked Issues: Relationships like “blocks” or “is blocked by.”

 Attachments: Related files or screenshots.

 Custom Fields: Additional fields tailored to project needs.

Jira Issue LifeCycle

Typical Jira Issue Lifecycle Stages

1. Creation / Open / To Do

 The issue is created and added to the backlog or project.

 It is unassigned or assigned to a team member.

 Priority, description, and other details are set.

2. In Progress / Assigned / Opened

 Work begins on the issue.

 The assignee updates the status to reflect active development or investigation.

 The issue may be discussed, updated, or reprioritized.

3. Review / Testing / Verification

 The work is completed and submitted for review or testing.

 QA or reviewers verify the fix or feature.

 The issue status changes to reflect testing phases like "In Testing," "Ready for
Review," or "Verification."

4. Done / Resolved / Closed

 The issue is confirmed fixed or completed.

 Status changes to "Done," "Resolved," or "Closed."

 The issue is considered complete and may be archived or referenced for future
audits.

5. Reopened (if necessary)

 If issues are found after closing (e.g., bugs reoccur), the issue can be reopened
and the lifecycle repeats.

Example: Bug Lifecycle in Jira

 New: Bug is reported and logged.

  Assigned: Assigned to developer for fixing.

 Open: Developer starts working on the bug.

 In Progress: Bug fix is underway.

 Resolved: Developer marks bug as fixed.

 Testing: QA tests the fix.

 Verified: QA confirms the bug is fixed.

 Closed: Bug is closed after verification.

 Reopened: If bug persists, it can be reopened.

Key Features Supporting Issue Lifecycle in Jira

 Custom Workflows: Define statuses and transitions tailored to your team’s process.

 Issue History: Jira records all changes, comments, and updates for transparency.

 Jira Query Language (JQL): Allows searching and filtering issues based on lifecycle states
and history.

 Automation: Automate status changes, notifications, and assignments to streamline

lifecycle management.

 Reports & Dashboards: Visualize progress and bottlenecks using burndown charts,
control charts, and release reports.

Benefits of Managing Issue Lifecycle in Jira

 Improves team transparency and accountability.

 Enables efficient tracking of work progress.

 Helps identify bottlenecks and delays early.

 Supports Agile and DevOps methodologies.

 Enhances communication among stakeholders.

Lifecycle Stage Description
Creation / To Do Issue is created and prioritized

In Progress Active work is being done

Review / Testing Work is reviewed and tested

Done / Resolved Issue is completed and closed

Reopened
Issue reopened if problems persist
(optional)

Working with Jira Issues

1. Creating Clear and Detailed Issues

 Write a concise summary that clearly states the task or problem.

 Provide a detailed description including context, steps to reproduce (for bugs), and
expected outcomes.

 Define acceptance criteria to clarify when the issue can be considered done.

 Use custom fields if needed to capture additional relevant information.

2. Prioritizing Issues

 Use Jira’s priority field (Low, Medium, High, Critical) to indicate urgency and importance.

 Apply prioritization techniques like MoSCoW (Must, Should, Could, Won’t) or value vs.
complexity to focus team efforts.

 Regularly review and adjust priorities based on project deadlines, dependencies, and
business impact.

3. Keeping Issues Updated

 Update issue status promptly to reflect current progress (e.g., To Do, In Progress, Done).

 Add comments to communicate questions, blockers, or progress updates.

 Attach relevant files, screenshots, or logs to provide additional context.

 Use labels and components to categorize and filter issues efficiently.

4. Collaborating on Issues

 Use @mentions in comments to notify team members and encourage collaboration.

 Assign issues to the appropriate team member responsible for the work.

 Add watchers to keep stakeholders informed about issue updates.

 Link related issues to show dependencies or duplicates.

5. Managing Workflows
  Understand and follow the custom workflows defined for your project to ensure
consistent progress tracking.

 Transition issues through statuses according to workflow rules and approvals.

 Use validators and conditions to enforce quality and process compliance.

6. Automating Repetitive Tasks

 Use Jira’s automation rules to auto-assign issues, send notifications, or update fields
based on triggers.

 Automate linking of duplicate bugs or escalating critical issues to reduce manual effort.

7. Using Filters and Dashboards

 Create and save filters to quickly find issues by criteria like assignee, priority, or sprint.

 Build dashboards with gadgets to visualize issue status, progress, and bottlenecks in
real-time.

8. Best Practices for Bug Tracking

 Provide a centralized help center or portal for users to submit bug reports.

 Allow multiple reporting channels (email, chat, widgets) to capture bugs easily.

 Encourage a culture of bug reporting and collaboration between development and IT

support teams.

 Link bugs to development work and automate notifications to keep reporters updated.

Summary Table: Working with Jira Issues

 Practice Description Tools/Features Used

Clear Issue Concise summary, detailed

Issue fields, custom fields
Creation description

Prioritization Use priority levels and methods Priority field, MoSCoW, filters

Status changes, comments,

Regular Updates Comments, status, attachments
attachments

Collaboration @mentions, watchers, linking Comments, watchers, issue links

Workflow
Follow workflows and transitions Custom workflows, validators
Management
Automate assignments and
Automation Jira Automation
notifications
Filters &
Save filters and create dashboards Filters, dashboards, gadgets
Dashboards
Bug Tracking
Centralized reporting, multi-channel Jira Service Management, portals
Best Practices

Jira workflow
A Jira workflow is a set of statuses and transitions that an issue moves through during its lifecycle—
from creation to completion. Workflows help teams standardize and visualize how work progresses,
ensuring clarity and control over processes.

Key Components of a Jira Workflow

 Statuses:
Represent the stages an issue can be in, such as To Do, In Progress, In Review, Done.

 Transitions:
Actions that move an issue from one status to another, e.g., Start Progress moves an issue
from To Do to In Progress.

 Conditions:
Rules that restrict who or when a transition can occur.

 Validators:
Checks performed before a transition to ensure inputs or conditions are valid.

 Post Functions:
Automated actions that happen after a transition, like updating fields or sending
notifications.

 Triggers:
Automated transitions triggered by external events, such as commits in Bitbucket.

Setting Up a Workflow in Jira (Step-by-Step)

1. Access Workflow Settings:

Go to Project Settings → Issues → Workflows → Add Workflow → Create New.

2. Design the Workflow:

Use the workflow editor to add statuses and connect them with arrows representing
transitions. Name transitions clearly (e.g., Start Progress, Resolve Issue).

3. Assign the Workflow to Issue Types:

Create or edit a Workflow Scheme associating your workflow with specific issue types (e.g.,
Bug, Task, Epic).

4. Associate Workflow Scheme with Project:

Link the workflow scheme to your project to apply it.

5. Test and Refine:

Create test issues and move them through the workflow to ensure it matches your process.
Best Practices and Tips

 Map Your Process First:

Discuss with your team the stages and transitions before building the workflow.

 Keep It Simple:
Start with essential statuses and transitions; add complexity only as needed.

 Use Conditions and Validators:

To enforce process rules and data integrity.

 Leverage Post Functions and Automation:

Automate repetitive tasks like notifications or field updates.

 Customize per Issue Type:

Different issue types (e.g., Bugs vs. Epics) may need different workflows.

 Visualize on Boards:
Configure Jira boards to reflect workflow statuses for easy tracking.

Example Workflow Stages

 To Do → In Progress → In Review → Done

 Open → Assigned → Resolved → Closed

 Backlog → Selected for Development → In Progress → Done

Jira Boards
What is a Jira Board?

A Jira board is a visual tool that helps teams track and manage their work as it moves through a
workflow. Boards display issues as cards organized into columns that represent different stages
(statuses) of the workflow.

 Boards provide a real-time view of work progress.

 They are essential for Agile practices like Scrum and Kanban.

 Boards can be customized to fit team processes and project needs.

Relationship Between Workflows and Boards

 A workflow defines the path an issue takes from creation to completion, consisting
of statuses and transitions.

 A board visualizes this workflow by mapping workflow statuses to columns.

 For simple workflows, each column corresponds to a single status.

 For complex workflows, multiple statuses may be grouped into one column to keep the
board manageable. For example, an “In Progress” column might include “In Development,”
“In Review,” and “Awaiting Feedback” statuses.

 Changes in workflow statuses are reflected on the board as issues move across columns.

Board Types

 Scrum Boards: Focus on sprint-based work, backlog management, and sprint planning.

 Kanban Boards: Focus on continuous flow, work-in-progress limits, and cycle time
optimization.
Advanced Board Configurations

 You can create multiple boards per project to support different teams or workflows.

 Cross-project boards aggregate issues from multiple projects, useful for leadership or cross-
functional teams.

 Boards can be tailored with features like swimlanes, quick filters, card colors, and
estimation settings for better visualization and control.

Configuring Boards and Workflows

 Boards are linked to filters that determine which issues appear.

 Board columns are mapped to workflow statuses via board settings.

 Workflow schemes associate workflows with issue types in projects.

 Advanced workflows may include conditions, validators, and post functions to control
transitions and automate actions.

 Workflow changes impact how issues appear and move on boards.

Aspect Description

Workflow Defines issue statuses and transitions (the process flow)

Visualizes workflow statuses as columns, showing issue

Board
progress

Board Columns Map to one or more workflow statuses

Advanced Multiple boards, cross-project boards, swimlanes, filters,

Configuration and automation

Workflow controls issue lifecycle; board provides a real-

Relationship
time visual representation of that flow