Video summary

JIRA CRASH COURSE for Beginners | Jira Tutorial | Jira Training | JIRA Project Management

Main summary

Key takeaways

Educational

Main Ideas, Concepts, and Lessons

1) Purpose and overview of the course (Jira crash course for beginners)

The video introduces Jira as a project management tool and explains that viewers will learn:

  • What Jira is
  • Core Scrum concepts needed to understand Jira
  • How to start using Jira immediately

The instructor presents an agenda covering:

  • Jira basics
  • Scrum concepts (including backlogs and ceremonies)
  • Jira issue types: epics, stories, tasks, bugs
  • Practical Jira actions: creating projects/issues, grooming/estimating, sprints, boards, filters, dashboards, workflows

2) What Jira is and what it’s used for

Jira (Atlassian) is described as a tool for:

  • Planning, tracking, and maintaining software projects

It’s widely used because it is said to be:

  • Easy to learn
  • Easy to customize
  • Adaptable to team needs

Jira supports many activities, including:

  • Requirements management
  • Task management
  • Bug tracking
  • Workflow optimization
  • Estimates and reporting
  • Project analytics and backlog tracking
  • Email notifications and release planning
  • Product mapping and more

The course uses Jira Cloud.

Starting an account: go to www.atlassian.com (including a free option for up to 10 users).

3) Scrum framework essentials (because Jira is Scrum-focused)

Scrum is presented as an agile-based framework for:

  • Defining
  • Planning
  • Executing
  • Delivering projects

Scrum is iterative and time-boxed (bounded by fixed time intervals).

Work is done in sprints:

  • Each sprint has a fixed duration set by the team
  • A sprint delivers a selected amount of work

Scrum team composition (3 roles)

Product Owner

  • Works with the customer
  • Collects requirements
  • Creates user stories from requirements
  • Maintains the product backlog
  • Guides what should be done and why
  • Only the Product Owner can delete items from the backlog (others can add)

Scrum Master

  • Acts as a servant leader
  • Ensures adherence to agile/scrum principles
  • Helps remove obstacles
  • Facilitates Scrum ceremonies and guides the team

Development Team

  • Cross-functional specialists who implement the project work

4) Backlogs and grooming

Product Backlog

  • A prioritized list of user stories
  • Managed by the Product Owner
  • Items are refined through discussion (backlog grooming)

Sprint Backlog

  • A subset of product backlog items selected for a sprint
  • Defines the scope of work for the upcoming sprint

Backlog grooming

  • Team discusses items to evaluate, refine, and prioritize them

5) Scrum ceremonies (what happens and when)

Core ceremonies mentioned:

  • Sprint planning
  • Daily standup
  • Sprint review
  • Sprint retrospective

Sprint planning

Before a sprint starts, the team meets to:

  • Discuss sprint scope
  • Finalize the sprint backlog
  • Define the sprint goal

Daily standup

A daily meeting (max 15 minutes) to:

  • Review what was done yesterday
  • Plan what will be done today
  • Identify obstacles

Each team member updates the status of remaining work on their tasks.

Sprint review

After the sprint ends:

  • Only completed user stories are released
  • A review meeting approves/validates the results

Sprint retrospective

The final sprint ceremony where the team discusses:

  • What went well
  • What needs improvement

6) Jira issue types: epics, user stories, tasks, bugs

Epics

  • Large work that must be split into smaller parts
  • Too big for a single sprint; spans multiple sprints

User stories

  • Smaller requirements the customer wants
  • Include only necessary information

Tasks

  • Work items that break down a story (story “elements”)

Bugs

  • Defects/errors/malfunctions in software
    • Example: system crashes when opening a module

Detailed Instruction-Style Methodology / Walkthrough (Jira setup and operations)

A) Create a Jira project (Scrum template)

  1. Click the “create project” button (right side).
  2. Choose a template:
    • Select Scrum
    • Pick a template like “project managed by a company” (advanced-feature template)
  3. Name the project:
    • Example: “my Jira project”
  4. Note:
    • The board exists but appears empty until epics/stories/tasks are created.

B) Create issues (epic → stories → tasks → bugs)

Use the Create button at the top to create different issue types.

Create an Epic

  • Select issue type epic
  • Enter an epic name
  • Fill fields such as:
    • Attachment(s)
    • Description/details
    • Priority (example mentions default “medium”)
    • Sprint assignment (not assigned yet because no sprints exist)

Link issues together

  • Epic relationships are used to connect related work.

Create a Story

  • Select issue type story
  • Provide description/details
  • Link the story to an epic
  • Add labels/tags:
    • Labels help with searching and organization

Create additional stories as needed

  • Stories can be:
    • Linked to the epic, or
    • Left unlinked if not currently related
  • Labels can separate work (example: “chapter one”, “chapter three”)

Create a Task

  • Select issue type task (the course references a “test task” example)
  • Ensure it appears as a separate type/icon on the backlog

Create a Bug

  • Select issue type bug
  • Provide description/details
  • Optionally add labels or sprint-like attributes (example sets a section/label)

Key behavior shown: Newly created issues accumulate in the backlog immediately (even before any sprint is created).

C) Plan and estimate work for a sprint

Conceptually in sprint planning:

  • Team selects which stories to include (example: 3 stories)
  • For each selected story:
    • Open it
    • Discuss it
    • Add tags if desired (example: “chapter one”)
    • Estimate using story points
      • Example story points given: 8
  • After estimation, proceed to create the sprint.

D) Create and start a sprint

  1. Click “Create Sprint”
  2. Add selected stories by dragging them into the sprint
  3. Set a sprint goal
  4. Start the sprint so the board can accept sprint tasks
  5. Move issues through board statuses as work progresses (example includes moving to “In progress”)

E) Configure the board (board settings)

  1. Open board settings via the three-dots menu (upper right)
  2. Change board layout by adding columns
    • Example: add a column called “Testing”
    • Movement is constrained by workflow rules (handled later via workflows)

Other visual/config options mentioned:

  • Card colors based on:
    • Task type
    • Priority (example changes priority to “highest” and “low” and notes card color changes)
  • Estimation settings:
    • Example mentions story point display configuration (could be changed to initial time estimate)

F) Complete a sprint (demonstration)

  • Move completed tasks to “Done”
  • Complete the sprint using sprint completion options
  • Note from the video:
    • Don’t end a sprint early unless appropriate (the demo ended when everything was done even though time remained)

G) Backlog behavior after sprint completion

  • After sprint completion, completed items disappear from the backlog view (as shown).

H) Create Jira filters (saved search criteria)

Filters are described as:

  • Saved criteria for frequently searched lists of tasks
  • Useful across boards, search, dashboards, and planning

Create multiple filters by defining criteria and saving them with names like:

  • “My Jira Filter”
    • Shows all tasks in the project (includes epics, bugs, stories, and completed ones)
  • “My Jira filter for section one”
    • Project equals My Jira Project
    • Label equals chapter one
  • “My Jira completed filter”
    • Project equals My Jira Project
    • Status equals completed tasks

The course emphasizes reusing filters later for dashboards.

I) Build a dashboard with gadgets

To create a dashboard:

  • Use dashboard options → Create dashboard
  • Name it and set permissions
    • Example: “my Jira project dashboard”
    • Available to the whole organization

Dashboard gadgets added (with filters)

  1. Pie chart gadget
    • Uses a filter (example: My Jira project filter)
    • Categorizes tasks by tags/labels
  2. Results gadget
    • Uses a filter (same section/label filter)
    • Config mentioned:
      • Number of results shown at once (example: 10; max 50)
      • Columns shown (task type, key, short description, priority, etc.)
  3. Created vs. resolution diagram
    • Uses a project filter
    • Configuration adjusted (example: show 5 days of data)
    • Displays how many tasks were created vs. resolved over time

Layout

  • Gadgets can be rearranged by dragging into dashboard columns.

J) Understand Jira workflows and edit them

Workflows are described as:

  • A set of statuses
  • Transitions
  • Task movement rules across a lifecycle

The course demonstrates viewing an existing workflow for “my Jira project,” including statuses such as:

  • To be executed
  • In progress
  • Testing
  • Done

Transition “arrows” indicate which statuses can go where.

Modify workflow (add a new status)

  1. Go to:
    • Project → Project settings → Workflows
  2. Edit and add a status
    • Example new status: “Pending deployment”
  3. Configure transitions
    • Allow transitions from all statuses to this status
  4. Set category placement
    • Example: placed under the “In Progress” category
  5. Publishing behavior:
    • Editing creates a draft
    • Apply changes via publish
    • Optionally keep a backup when publishing (with a chosen name)

Verify the workflow change

  • Return to the project and check the new status appears (example: “Awaiting Deployment”)
  • Update the board configuration:
    • Board settings → Columns → add column
    • Add a column for the new status (example column: “Pending Deployment”)
  • Tasks with that status can now appear there according to workflow rules.

Speakers / Sources Featured

  • Speaker/Instructor: Ritikauri (from Management Bliss)
  • Website/source for Jira: Atlassian — https://www.atlassian.com
  • Website/source for the course: Management Bliss (referenced as www.managementbliss.com / also www.mmanagementbas.com as written in subtitles)
  • Mentioned video/source (YouTube): “What are sprints in agile” (Management Bliss channel)

Original video