Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,365,108
Community Members
 
Community Events
168
Community Groups

Common Jira Terms and Concepts

Question

What is a Jira issue and a Jira project?  Why are users often confused by these terms?  Why are things named the way they are?

Answer

Jira terminology is strange at first and even foreign if you’re using Jira to track business processes.  Jira began as a bug tracking tool for software development teams and morphed into an issue tracker and project management tool for all teams.  Some of the naming reflects its origins and the need for somewhat generic terminology so it can support #allthethings.  Further, your organization may have introduced additional custom naming or language translations, which can add to the confusion.

Here are three fundamental Jira terminology concepts to understand:

Issue – an individual item in Jira

Why the confusion?  The dictionary defines “issue” as “an important topic or problem for debate or discussion”.  In Jira however, an “issue” represents all types of requests including:  things to do, tasks, bugs and defects, new features, improvements, changes, incidents, tickets, problems, etc.  An issue is a single unique record of any type, regardless of its content or the scenario.   Requests like “I need a new desk phone” is an issue just like “Create a new product” and “The server is down!” are issues.  Each Jira issue has a unique key in the format:  KEY-123.

Project – a collection of Jira issues

Why the confusion?  Teams have their own internal initiatives or strategic priorities they often call “projects.”  Yet in Jira, a collection of issues is also called a project!  For example, the Marketing team’s many internal projects are tracked in their one Jira project.  Think of a Jira project is a bucket that contains a “to do” list.  Projects are often set up per department, per team, or to track large initiatives with a known end date.

Issue Type – a classification of issues in a Jira project

Why the confusion?  Each Jira issue can be of a different type.  For example, you may use a “Bug” type to report a defect and a “Feature” type to request new functionality.   Each Jira project can have its own set of available issue types.   A development project may have issue types like:  Feature and Bug and a Legal project may have issue types like: Task and Sub-task.  Different issue types allow for different fields, different workflows, or both, within the same Jira project.

Not sure which issue type to select?  Just make your best guess.  An issue can easily be changed later using Jira’s “Move” command.

Regardless of the wording, you can use Jira to:  schedule and record work, manage your project pipeline, report and fix bugs, triage issues, report time and monitor progress, track changes and tasks, and keep a authoritative, historical, and legal record of work.

3 comments

Tuncay Senturk Community Leader Jan 26, 2019

Nice article @Rachel Wright, thanks.

 

I think the most common terminology difference that we face is the term "project". For PMO project can be a bunch of issues which costs more than some specific man/hour calculation, and it has start/end dates. Unlikely, Jira's projects may live forever without an end date, they have versions instead.

Anyway, great article.

nice.jpeg

issues are projects with no urgent end date. A to do list of many issues. A single issue can be immediate and urgent.

The need to write such an article is interesting in itself. I'm just getting to grips with Jira after using Trello for years, and am struggling to get my head around the "issue" terminology, hence a Google search brought me here.

As you mention, an "issue" most commonly refers to a problem that needs solving, such as a bug. I think it's dangerous to fight against dictionary definitions when naming product features, such as the case with your use of "issue". 

Trello did this well, simply by not trying to label work or tasks as anything, and letting the user define their own terminology with the use of simple "cards". 

Of course, not an easy problem to solve due to the history of Jira as bug-tracking software, so it will be interesting to see how the Jira terminology evolves.

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events