Interactive Jira training
Hands-on Jira practice for beginners
Learn Jira by using it. Agile Board Practice gives you short, interactive lessons on a practice board that works like Jira. Read a ticket, move work across the board, create stories and bugs, and handle the kind of requests that land in your inbox at work. Every step checks what you did and tells you why.
- No Jira account needed
- Nothing you click can break anything
- About 25 minutes for the basics
Why Jira feels hard at first
Most people meet Jira in their first week on a new team. Someone sends a link to a board, a ticket gets assigned to you, and everyone else seems to know what the columns, flags and story points mean. Asking feels awkward, and clicking around a live project feels risky, because every change you make is visible to the whole team.
Video courses explain the screens, but watching someone else click does not build the habit. A free trial gives you an empty project with nothing in it to practise on. What most beginners need is a safe place to try the everyday tasks, with something telling them whether they got it right.
That is what Agile Board Practice is for. It is a practice board with real-looking work already on it, and a lesson that walks you through it one step at a time.
How it works
Read the task
Each step starts with one clear instruction in plain language. New words are explained the first time they appear.
Do it on the board
Under the instruction is a practice board that behaves like the real thing. Open tickets, drag cards between columns, change the status, assign work and write comments.
Get instant feedback
The lesson checks what you did. A right answer explains why it is right. A wrong one tells you where to look, so you learn the reason and not just the click.
Lessons build on each other. You start by reading a single ticket and finish by running a busy board two days before the end of a sprint.
What you will learn
Six short lessons cover the work most people do in Jira every day.
-
Read a ticket
Find the key, summary, status, assignee, reporter and priority, and read the description and comments the way experienced team members do.
-
Read the board
Understand columns and statuses, count the work in progress, filter the board by person, and spot a flagged ticket that is stuck.
-
Move your work
Start a ticket, move it through the workflow by dragging the card or with the status button, leave a useful comment and hand it over to a tester.
-
Create a ticket
Choose between a story, a bug and a task, write a summary that makes sense on its own, add a description someone else can act on, set an honest priority and link the ticket to an epic.
-
Find anything
Search by ticket key or by words, and see which epic a ticket belongs to, so you can answer “where is that one?” in seconds.
-
Run a busy board
Pick the most urgent work, close what has passed testing, clear a blocker and send failed work back, all on one crowded board.
Workplace practice: from your inbox to the board
Knowing the buttons is half of it. The other half is knowing what to do when a real request arrives. In workplace practice, an email appears on the left and the board is on the right.
- Your product owner asks whether a fix is ready for a client. You find the ticket, read its status and comments, and choose the reply that tells the truth.
- A developer says a fix is live and asks you to close the ticket. You move the right one to Done and leave a note.
- Compliance needs a new field by a legal deadline. You log it with the right type and priority, and put the deadline where the team will see it.
- Customer support reports a bug. You search first, find that it is already being fixed, and add the new reports to the existing ticket instead of creating a duplicate.
Every reply is checked against what is actually on the board, the same way a colleague would check it.
Puzzles against the clock
Once the basics feel easy, puzzles keep them sharp. Each puzzle is one busy board and one problem: find who to ask, find what is blocking a release, clean up the review column before the sprint review, or follow a chain of linked tickets to the real cause. Every puzzle has a par time. Beat it for bonus points, and see how your time compares with other learners.
Who it is for
- New joiners whose team works in Jira from day one
- Career switchers who see “Jira experience” in job ads and want to practise before an interview
- Business analysts, product owners and scrum masters who write and organise tickets
- Testers who move work through review and send failed tickets back
- Managers and stakeholders who mostly read boards and need to understand what they are looking at
- Anyone coming back to Jira after a break, or moving over from another tool
You do not need a Jira account or a technical background. If you can use email, you can do these lessons.
For teams and companies
Onboarding people into Jira usually means a long video playlist, or a colleague giving the same walkthrough again and again. Agile Board Practice gives every new team member the same hands-on start, at their own pace, without touching your real projects.
Team plans will include licences for groups of learners and a simple view of who has finished which lessons. If you are planning Jira training for a team, join the waitlist with your work email and choose “buying for a team”. We will get in touch before early access opens.
Jira terms explained
The words you will hear in your first week, in plain language.
- Ticket (issue)
- One piece of work: a bug to fix, a feature to build or a task to do. Everything about it, from the description to the discussion, lives on the ticket.
- Key
- The unique ID of a ticket, such as PAY-142. The letters are the project and the number counts up. Keys never change, so they are the safest way to refer to a ticket.
- Board
- A view of the team’s tickets arranged in columns, one column per status. Scrum boards show the current sprint. Kanban boards show a continuous flow of work.
- Status
- Where the work is right now, for example To do, In progress, In review or Done.
- Assignee and reporter
- The assignee is the person doing the work. The reporter is the person who created the ticket.
- Priority
- How urgent a ticket is, from Lowest to Highest. It tells the team what to pick up first.
- Sprint
- A short, fixed period, often two weeks, in which the team commits to a set of tickets.
- Backlog
- The list of work that is not in the current sprint yet, ordered by importance.
- Epic
- A large goal split into many smaller tickets, such as a redesign of the receipts screen.
- Story
- A ticket for something new that users need, often written from the user’s point of view.
- Bug
- A ticket for something that is broken. A good bug report says what happened, how to make it happen and what should happen instead.
- Task
- Work that is neither a new feature nor a bug, such as updating a document or renewing a certificate.
- Story points
- A rough estimate of effort, used to plan how much work fits into a sprint.
- Flag
- A marker that a ticket is stuck. The latest comment usually says what it is waiting for.
- Blocked by
- A link between two tickets. If ticket A is blocked by ticket B, A cannot move until B is done.
Frequently asked questions
Is this the real Jira?
No. Agile Board Practice is an independent practice tool with its own board that works the way Jira boards do: tickets, statuses, assignees, priorities, epics, sprints and links. The skills carry over directly to Jira and to similar tools.
Do I need a Jira account?
No. Everything runs in your browser on practice data. Nothing you do touches a real project, so you can make mistakes freely.
How long does it take to learn the basics of Jira?
The six basic lessons take about 25 minutes in total. Workplace practice tasks and puzzles take two to five minutes each, so they fit into a coffee break.
What will it cost?
Joining the waitlist is free. The first lessons will be free to try. The full course is planned as a one-time payment per learner, with team pricing for companies.
Does it cover Jira Cloud and Jira Data Center?
The lessons teach what both have in common: reading and creating tickets, moving work across a board, sprints, epics and links. Buttons can look a little different between versions, but the habits are the same.
Is it for Scrum or Kanban teams?
Both. The lessons use a sprint board, and the same skills apply to Kanban boards, which are columns of statuses without a sprint.
Can my company buy it for a team?
Yes. Team plans are planned. Join the waitlist with your work email, choose “buying for a team”, and we will contact you before early access opens.
When does it open?
Early access opens to the waitlist first. We will send one email when it does.
Who makes it?
Agile Board Practice is made by ozols.dev, a one-person software studio in Latvia. You can reach the maker directly at emils@ozols.dev.
Get early access
Join the waitlist and be first to try the lessons. One email when early access opens.