Blog Barista: Sam Nadarajan | January 8, 2020 | Developer Tools | Brew time: 6 min
If you are reading this post, then you are probably new to Jira! If so, congratulations on choosing one of the best online tools for project collaboration. This first post from the five part Jira 101 series will help you become familiar with some basic Jira concepts. By the end of this post, you will be familiar with some of the core terminology and have a better understanding of the layout of the Jira ecosystem.
What is Jira?
At its core, Jira is a collaborative online tool for managing and working on projects. Jira is built and maintained by Atlassian, an Australian company that builds a number of different products including Confluence, Bitbucket, and Bamboo. If you have ever used Trello (now owned by Atlassian) or Asana for simple task or project management, Jira offers significantly greater functionality than those tools. Small businesses specifically can benefit from this product as it will properly scale as they grow. But, the benefits of using Jira increase the larger and more complex your organization becomes.
What is the difference between all the “Jiras”?
As you research Jira’s documentation online, you may notice that there are a number of different “Jiras” such as Jira Core, Jira Software, and Jira Service Desk. Here is a brief breakdown of their differences:
Think of Jira Core as the foundation that the rest of the platform is built on. If you are using Jira to manage non-technical projects, this is probably what you are using. Jira Core provides users with the ability to manage business projects, tasks, and processes. Think of a simple to-do application you currently use, add a few extra bells and whistles such as designing workflows, changing the status of issues, collaborating with others, and configuring dashboards, and you have Jira Core.
If Jira Core is the foundation, Jira Software is a very large skyscraper built on top of the Core platform. Geared towards technical project management, Jira Software provides project artifacts for Scrum and Kanban methodologies. Jira Core is included with Jira Software, so your organization still has the ability to manage projects at a simpler scale.
Jira Service Desk
As its name implies, this is Atlassian’s answer for service desks within an organization. Jira Service Desk serves as a smaller skyscraper to Jira Software that is built on the same Jira Core foundation. Jira Service Desk will be addressed in greater detail in an upcoming blog post, but for now understand that Jira Service Desk is a separate product that lives on top of the Jira Core platform.
Core Jira Concepts
Regardless of whether your organization adopts Jira Core, Jira Software, or Jira Service Desk, the following concepts apply to all three.
Issues form the building blocks of the Jira ecosystem, and contain configurable information such as details, important dates, the people involved with the issue, and comment threads – among other features. Reports and other metrics are predominantly driven by an aggregation of issues. If you are working on PROJ-1 or SAMP-323, you are working on different issues.
While “issue” is the official terminology, you may often hear the term “ticket” used interchangeably.
If issues are the building blocks, projects serve as the containers holding those building blocks. Projects define the scope that your issues pertain to, and every issue must belong to one project.
Jira Core offers business projects that may pertain to an initiative or business unit within an organization, while Jira Software adds software projects that may pertain to different applications built and supported by your organization. Jira Service Desk adds another project type – Service Desk – to the list.
All issues begin with the project key that is defined when the project is created. For example, “My New Project” may define the key “PROJ”. All issues for “My New Project” will be labeled as “PROJ” followed by a unique identifier (e.g. PROJ-1, PROJ-234, PROJ-1844).
Filters serve as another type of container that holds issues. Filters are defined by queries written in the Jira Query Language (JQL) that can pull issues based on user-defined criteria. They can contain issues within one or more projects, with additional criteria based on the date or fields within those issues. Once defined, these filters can be saved and used to populate boards and dashboards.
By default, filters that you create are only accessible by you. However, you have the ability to share filters with others by giving other user groups permission to view or edit your filters. We will discuss filters in greater detail in Part 3 of the Jira 101 series.
Boards serve as a visual access point to view and manage issues. If your organization is using Jira Software, you may have Scrum or Kanban boards configured to allow your team to move issues across an interface. Boards can be tied to a specific Jira Software project or a saved filter. While boards can be directly associated with a specific Jira project, having a saved filter drive a board’s issues allow multiple Jira projects to be displayed in the same board with a shared backlog.
Regardless of the configuration, you will most likely access your board as part of your daily workflow and work on issues assigned to you. We discuss more about boards later in Part 4 of this series.
When you log in to Jira, the first page you will see is the Dashboards page. You have the ability to configure gadgets that feed you certain data based on the criteria you specify. Jira provides a number of default gadgets ranging from issue lists to bubble charts. Many of the gadgets are fed by saved filters, so you can write a number of filters beforehand and configure gadgets that extract that data for easier viewing.
Like saved filters, dashboards can be shared with other Jira users. Each user receives a default personal dashboard that can be configured. Jira administrators may configure the system dashboard for the entire organization. Based on global permissions, users may configure additional dashboards that showcase different kinds of information for different types of users. For example, an organization may decide to set up dashboards for managers, developers, directors, or other types of users. This allows key metrics to be configured once and viewed on an as needed basis.
These core concepts will become more intuitive the more you work in Jira. Having a proper understanding of these concepts will assist you as you navigate the Jira ecosystem and continue through this blog series.
Make sure to check back in to catch the rest of the Jira 101 series:
Other recent posts:
Blog Barista: Sam Nadarajan | February 12, 2020 | Developer Tools | Brew time: 9 min
Welcome back. We’ve made it to our last part of the Jira 101 series! Throughout the series, we’ve In today’s post, we will take a closer look at the Jira Service Desk.
Whether your company has adopted Jira Service Desk as their tool of choice for service desk operations or your company is in the middle of evaluating existing Service Desk tools, understanding the basic…
Blog Barista: Sam Nadarajan | February 11, 2020 | Developer Tools | Brew time: 7 min
Welcome back to the Jira 101 series. If you’ve been following along, then you should now have a basic understanding of Jira’s core concepts and terminology, know how to navigate the issue detail view, and perform robust searches on issues within Jira. In today’s post, we will take a…