How to learn Jira: a free path from beginner to skilled

The short answer

Learn Jira in three layers, in this order. First, learn the five everyday skills that every Jira user needs: read a ticket, read a board, move your own work, create a ticket and find things. Second, learn how your team has set Jira up: its columns, statuses and work types. Third, add search and a few shortcuts so you can find anything without asking. You can do all three for free.

The fastest way through the first layer is hands-on practice on a board where mistakes cost nothing, not watching someone else click. The second layer you can only learn from your own team, so ask early. Certifications come last, if at all: most of Atlassian's Jira exams are aimed at people who administer Jira, and even the entry-level Jira Essentials exam is paid (see Is there a free Jira certification?).

Step 1: Learn the words first

Jira is easier once the vocabulary stops getting in the way. Part of the confusion is that the same thing can have two names, because Atlassian renamed things recently:

• Work item, issue or ticket. One piece of work. On 9 October 2024 Atlassian announced it was retiring "issues" as the default name, and its current Jira Cloud help pages say work item. Colleagues may still say issue or ticket. This guide says ticket.
• Space or project. Atlassian's current help pages describe a space as "a collection of related work items that helps your team organize, track, and manage work". Older pages and many people still say project.
• Key. Each space has a space key that prefixes all its work items, so PAY-142 is ticket 142 in the PAY space.
• Board, backlog, sprint, status, assignee. The beginner's guide to using Jira explains each one in a sentence.

When you search Atlassian's help pages, try both names. A search for "issue" can lead you to an older page, which may describe menus that have since moved.

Step 2: Find a safe place to practise

Worrying about breaking something slows learning down. If you are worried that dragging a card will notify ten people, you will ask a colleague instead of trying. So before you learn the skills, find somewhere to practise them. You have three free options:

1. A practice board outside Jira. No account, no admin, nothing you do reaches a real team. Agile Board Practice works this way: its lessons run on a self-contained practice board, so every click is safe.
2. Your own Jira Cloud Free site. Atlassian's Free plan is for up to 10 users and includes 2 GB of file storage. You can create a space, make up a few tickets and try every menu. Keep it for practice: do not copy real work data into it without your employer's permission.
3. A training space at work. If your company allows it, ask for a space called "Training". Team-managed spaces are "set up and maintained by anyone on the team", while company-managed spaces need a Jira admin, so who can create one depends on your site.

Step 3: Learn the five everyday skills, in order

Each skill builds on the one before, so do them in this order and do each one rather than read about it:

1. Read a ticket. Find the key, summary, status, assignee, priority, description and the newest comments. Practise until you can answer "where is PAY-142 and who has it?" in ten seconds.
2. Read the board. Know what each column means and filter the board to one person. Work moves left to right.
3. Move your own work. Start a ticket, comment on it, hand it on. The guide on changing status in Jira covers the board, the ticket and bulk changes.
4. Create a ticket. Pick the right type, write a summary that makes sense on its own and set an honest priority. See how to write a good Jira ticket and story vs task vs bug.
5. Find things. Search by key when you know it, by words when you do not. Step 5 takes this further.

A good test that you have these down: a colleague, say Jonas from product, messages "Is the login timeout fixed? Can I tell the client?" You find the ticket, read its status and latest comment, and reply with where it is, what happens next and when. If you can do that without help, you have the core of Jira.

Step 4: Learn how your team uses Jira

Every Jira setup is different. Two teams in the same company can have different columns, statuses and rules for the same kind of work. That is why "knowing Jira" from one job does not fully transfer to the next, and why this step matters as much as the clicks. In your first week, ask a teammate these questions and write down the answers:

• What does each column mean, and who moves cards into and out of it?
• Do we work in sprints (Scrum) or in a continuous flow (Kanban)? The Scrum vs Kanban board guide explains the difference.
• Which work types do we use, and when?
• What counts as done? Is there a review or testing column before it?
• Who creates tickets: only the team, or anyone who asks for work?

If a column name makes no sense to you, it is a normal question. The Jira workflow guide shows how statuses and transitions sit behind those columns.

Step 5: Get fast with search and shortcuts

Being skilled at Jira mostly means finding things quickly and moving without the mouse. Two habits get you there.

Learn a little JQL

JQL, the Jira Query Language, is what advanced search uses to find work items. Atlassian notes that it uses SQL-like syntax but is not a database query language, so you do not need to be technical. To try it in Jira Cloud:

1. Select Search in the top navigation, or press /.
2. Select View all work items.
3. If basic search appears, select JQL.
4. Type a query such as project = "PAY" and press Enter.

Once a search is useful, save it as a filter so you can run it again tomorrow.

Learn three shortcuts

In Jira Cloud, press C to create a new work item and I to assign a work item to yourself. Press ? on any page, or select Help, then Keyboard shortcuts, to see the full list.

Free training from Atlassian

Atlassian made its on-demand courses at Atlassian University free on 1 May 2024; before that they cost $39 each. Two free options suit beginners:

• "Get the most out of Jira", a learning path of about 1 hour 30 minutes in three courses: getting started, tracking your work, and personalising how you work in Jira.
• "Get started with Jira", a free 60-minute class with a live instructor.

These courses show you Jira's features. They pair well with a practice board, where you do the steps yourself, and with Step 4, which no course can do for you. Atlassian also notes that what you see in a course depends on your app subscription, so some screens may differ from your company's Jira.

Is there a free Jira certification?

Not for Jira itself. Atlassian separates free certificates, whose exams are free and unproctored, from paid certifications, whose exams are proctored and paid to the test provider. Its free certificates today cover tools such as Jira Service Management rather than Jira, so a Jira user or admin credential means a paid exam. Preparation can still be free: for example, Atlassian's page for the Managing Jira Projects for Cloud certification offers free on-demand training to prepare, says the exam "is now available at half price", and says the certification will be retired in January 2027, with its content moving into the Jira Administration for Cloud certification.

That page describes it as for "Jira project admins". Atlassian also has an entry-level Jira Essentials certification, which its page describes as for "current and future Jira users". Free on-demand training prepares you for it, but the exam is paid too. Either way, a certification is not where to start. Learn the everyday skills, use them on real work for a few months, and then decide whether a user or admin certification fits the job you want.

How to show Jira skills on your CV

"Jira" on its own in a skills list says little, because it can mean anything from reading tickets to running a company's whole setup. Say what you did with it. Some examples, adjusted to your own work:

• "Managed my team's support requests in Jira: triaged new tickets, set priorities and linked duplicates."
• "Tracked testing in Jira on a Scrum team: wrote bug reports with steps to reproduce and moved work through review."
• "Built saved filters in Jira (JQL) for weekly status reporting to stakeholders."

If you have not used Jira at work yet, say what you practised and how: for example, the Atlassian courses you completed, or that you can read a board, create tickets and search with JQL. Then be ready in an interview to describe one ticket from start to finish: how it was created, who moved it, and how you knew it was done.

Learning Jira and Confluence together

Some teams pair Jira with Confluence, Atlassian's wiki, for longer documents such as requirements and meeting notes. Learn Jira first, because that is where your daily work lives, then learn how the two link up. The guide on using Jira and Confluence together covers the basics.

Practise before it counts

The quickest way to get good at Jira is to do the steps, get them wrong somewhere safe, and see why. Agile Board Practice is built for that. Six short lessons of 3 to 5 minutes follow the order in Step 3: read a ticket, read the board, move your work, create a ticket, find anything, and run a busy board near the end of a sprint. Workplace tasks put a colleague's email next to the board, such as a product owner asking for a status update, and timed puzzles ask you to solve a problem on a busy board, such as finding what blocks a release. Every step confirms when you get it right, quiz answers and many steps explain why, and nothing you click touches a real Jira.