Skip to content
Tutorials Center
My learning

Topics

Lesson 13 of 29 ยท Jira Basics

Getting Started with Jira

A beginner's tour of Jira Cloud: sites, projects, team-managed versus company-managed, issue keys, navigation and templates, with runnable stand-ins.

Jira is a work-tracking tool from Atlassian. Software teams use it to keep a backlog, plan Sprints, track bugs and see what is happening, but teams in marketing, HR and operations use it too. It is the most common tool for the ideas in this tutorial: the Product Backlog, user stories, boards and reports all have a place in Jira.

This lesson is a guided tour of the basics: the pieces Jira Cloud is made of, how a project is set up, the two project styles, and how to find your way around. Jira is a web application, and the real thing cannot run inside this site, so the walkthrough below describes the screens in words and the commands are read-only. The runnable examples are small JavaScript stand-ins that model projects and issue keys, so you can see the logic behind what Jira does. They are not Jira, and the real product has far more features.

Jira's menus, labels and plans change often. Treat the screen names here as a guide to what to look for, and check the current Atlassian documentation when something looks different in your site.

The building blocks

Site Your company's Jira address.
Project A container for related work.
Issue One piece of work, such as a story.
Issue key A short unique ID like WEB-12.
1 / 2

Sites, products and projects

You get Jira by signing up for a site, an address such as https://yourcompany.atlassian.net. That address is where your whole organization works. Jira Cloud is hosted by Atlassian, so there is nothing to install. Large companies sometimes run their own installation (Data Center), but the concepts in this tutorial apply to both.

Atlassian sells several Jira products that share a site, including Jira (for software and business teams), Jira Service Management (for support desks and IT) and Jira Product Discovery (for roadmaps and ideas). This tutorial focuses on Jira for Scrum and Kanban teams. Plans change over time, and a free plan for small teams has existed, but check Atlassian's pricing page for current limits.

A site contains projects. A project is a collection of related issues (the pieces of work), plus its own board, backlog and settings. A small company may have one project; a large one may have hundreds, such as one per product or team.

An issue is a single item of work: a story, bug, task or epic. Issues, Issue Types and Workflows covers them in depth. For now, remember that every issue has a key made of the project key, a dash and a number, for example WEB-12. The key is unique across the site, shows up in links and commit messages and is the quickest way to refer to a piece of work.

Creating a project

You create a project from the Projects menu in the top bar, then choose Create project (the exact wording may vary). Jira walks you through a few choices.

Choose a template

A template sets up a starting board and workflow. The names available depend on the plan and project style, but typical options include:

  • Scrum: a backlog, Sprint planning and a Sprint board. It matches the framework in Scrum at a Glance.
  • Kanban: a board with columns and no Sprints, suited to continuous flow (Kanban and WIP Limits).
  • Bug tracking: a simple setup for logging and fixing defects.
  • Task or work tracking: a general list-style template for non-software work.

Choose the one that is closest to how the team already works. Everything it creates can be changed later, though some choices (like Scrum versus Kanban) are easier to adjust in some project styles than others.

Choose a name and a key

You give the project a name ("Web Shop") and a key ("WEB"). The key becomes the prefix of every issue key in the project. Jira suggests a key from the name, and you can edit it. The key must be unique in the site, begins with a letter and is typically short, capital letters. Choose it carefully: it appears everywhere, and changing it later is possible but disruptive for links and habits.

Team-managed versus company-managed

When you create a project, Jira asks which kind of project you want.

Team-managed Company-managed
Who configures it Project admins in the team Jira administrators
Where settings live Inside the project In shared schemes used by many projects
Best for A single team that wants to move fast Organizations that need consistency and governance
Customization Simple, per project Deep and shared, with more options
Older names "Next-gen" "Classic"

A team-managed project is quick to set up: the team can change its own issue types, fields, workflow and board without asking anyone. Because the settings belong to the project, two team-managed projects can differ greatly. A company-managed project uses schemes (shared sets of rules for workflows, fields and permissions), which administrators control for many projects at once. It takes longer to set up but lets a company enforce a standard process and report across many teams. Workflows, Permissions and Customization goes into schemes in detail.

If you are unsure, start with team-managed for a single team. Atlassian provides ways to move between the types, but they are not always seamless, so think about it before you build up a large project.

Finding your way around

The layout changes occasionally, but the main areas are stable.

The top bar is available everywhere. It usually contains links such as Your work (items assigned to you), Projects (recent and starred), Filters (saved searches, see JQL and Filters), Dashboards, Teams and Apps. A prominent Create button makes a new issue, and a search box finds issues by text or key.

The project sidebar appears on the left once you open a project. Common entries include:

  • Summary or Timeline: an overview, or a roadmap of epics.
  • Backlog: the ordered list of work (Scrum projects) with Sprint sections.
  • Board: the visual board with columns for each status.
  • List: the issues in a table.
  • Reports: burndown, velocity and similar charts (Jira Reports and Dashboards).
  • Project settings: names, access, issue types, workflows, notifications.

An issue opens either in a side panel or on its own page at /browse/WEB-12. It shows a summary (title), description, status, assignee, labels and a comment stream.

The keyboard shortcut c opens the Create dialog on many Jira pages and / jumps to search, so you can move quickly once you know the issue keys. Shortcuts can be turned on or off in your profile settings.

A first walkthrough (read-only)

For a new team, the first ten minutes in Jira usually go like this:

  1. Sign in to your site and open Projects > Create project.
  2. Pick Scrum, choose team-managed, name it "Web Shop" and accept the key WEB.
  3. Invite your teammates from the project's access settings.
  4. Click Create and add your first stories to the backlog (User Stories and Acceptance Criteria helps you write them).
  5. Open the Board to see the To Do, In Progress and Done columns that the template created.

None of this needs code, but Jira also has a REST API for automation, which you will meet in Jira Automation and the REST API.

Stand-in 1: projects and issue keys

The program below models the part of Jira you just read about: a site holds projects, each project has a unique key and a counter, and each issue gets a key made from the project key and the next number. It also rejects keys that are badly formed or already taken.

In real Jira the key rules are a bit more detailed and an administrator can configure them. This stand-in uses a simple rule: an initial capital letter, then 1 to 9 capital letters or digits. The point is the logic of unique prefixes plus counters, not an exact copy of Atlassian's validation.

JS Model a site, projects and issue keys

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Two things are worth noticing. First, each project keeps its own counter, so WEB-2 and OPS-2 can both exist but never WEB-2 twice. Second, the two bad attempts fail with clear messages, which is the same idea as Jira refusing a duplicate key. Try adding a third project with the key OPS and read the error.

Stand-in 2: choosing a template and finding keys

The second program is a tiny decision helper that mirrors the guidance above: Scrum if you plan in Sprints, Kanban for continuous flow, a service-style template for request queues, and company-managed when you need shared control. It then shows how tools find issue keys in free text, which is how Jira links a commit message or chat message to an issue.

JS Recommend a template and spot issue keys

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The helper is deliberately simple: real decisions involve budgets, existing tools and how much process the organization needs. Its value is in making the questions explicit. The last lines show a regular expression finding WEB-12, WEB-2 and OPS-31 but ignoring ABC_1 and the lowercase web-4, because keys are capital letters. Jira's integrations with Git hosting services use this idea to link commits and pull requests to issues when a key appears in a branch name or message.

Common beginner mistakes

  • Creating a project per person. Projects should map to a product or a team, not an individual.
  • Over-customizing on day one. Start with the template, work for a Sprint or two and then adapt.
  • Choosing the wrong project style and not knowing it. Decide early whether you need shared company settings.
  • Using Jira as the plan itself. Jira stores the work, but the conversation, the goals and the Sprint Goal are still the team's job.
  • Duplicate trackers. If half the team uses spreadsheets and half uses Jira, nothing is true.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is an issue key such as WEB-12 made of?

    The project key (WEB) identifies the project and the number counts the issues created in it. The result is a unique key across the site.
  2. 2. Which description matches a team-managed project?

    Team-managed projects keep their configuration inside the project. Company-managed projects use shared schemes controlled by administrators.
  3. 3. Your support team handles a continuous stream of requests with no fixed iterations. Which template is the closest starting point?

    Kanban boards suit continuous flow. A service-oriented template may also fit if the team handles requests from other people.
  4. 4. Why does a stand-in program like the one in this lesson help you learn Jira?

    The stand-ins model ideas such as unique keys and per-project counters. They do not talk to Jira, and the real product does much more.

Summary

  • Jira Cloud is accessed through a site. A site holds projects, and a project holds issues.
  • Every issue has a unique key built from the project key and a number, such as WEB-12.
  • A template (Scrum, Kanban, bug tracking, task tracking) gives you a starting board and workflow.
  • Team-managed projects are configured by the team itself, while company-managed projects use shared schemes controlled by administrators.
  • The top bar and project sidebar are the main navigation. The Backlog, Board and Reports are the areas Scrum teams use most.
  • The runnable examples are stand-ins for the logic of keys and templates. They do not replace or connect to Jira.

Next, look closely at the work items themselves in Issues, Issue Types and Workflows.