# Concepts in JIRA

> ### New to JIRA? Follow these steps to get started: [Jira Project Management Tool](https://techbrary.hashnode.dev/jira-project-management-tool)

### **Basic Concepts in JIRA**

#### **1\. Project**

A collection of tasks, bugs, or features related to a specific goal or product.

#### **2\. Issue**

A task, bug, story, or any work item tracked in JIRA.

#### **3\. Issue Types**

* **Task** – A general work item.
    
* **Bug** – A defect or problem in the system.
    
* **Story** – A user requirement or feature request.
    
* **Epic** – A large feature broken down into smaller stories.
    

#### **4\. Workflow**

The process an issue follows from start to completion, including statuses like **To Do, In Progress, In Review, Done**.

#### **5\. Board**

A visual representation of tasks in a project, either **Scrum (Sprint-based)** or **Kanban (Continuous workflow)**.

#### **6\. Sprint**

A fixed time period (e.g., two weeks) where a team works on selected tasks. Used in Scrum projects.

#### **7\. Components**

Subsections within a project to organize issues (e.g., Frontend, Backend).

#### **8\. Labels**

Tags used to categorize and filter issues easily.

#### **9\. Assignee**

The person responsible for working on an issue.

#### **10\. Reporter**

The person who created the issue and tracks its progress.

#### **11\. Backlog**

A list of tasks, bugs, or stories that are yet to be worked on. Mainly used in Scrum projects.

#### **12\. Priority**

Defines the importance of an issue. Common priorities include **High, Medium, Low, and Critical**.

#### **13\. Resolution**

Indicates how an issue was completed, such as **Fixed, Won’t Fix, Duplicate, or Incomplete**.

#### **14\. Versions (Releases)**

Represents different software versions where issues are planned, tracked, and released.

#### **15\. Subtasks**

Smaller tasks within a main issue to break down work into manageable parts.

#### **16\. Watchers**

Users who follow an issue to get updates but are not assigned to it.

#### **17\. Roadmap**

A high-level view of planned features and development timelines.

#### **18\. Issue Linking**

Allows connecting related issues (e.g., blocking, duplicates, relates to).

#### **19\. Permissions**

Controls what actions a user can perform based on their role in a project.

#### **20\. Filters**

Custom queries to find and organize issues based on specific criteria.

### **Advanced JIRA Concepts**

#### **21\. Custom Fields**

Additional fields that can be added to issues to store specific information.

#### **22\. JQL (JIRA Query Language)**

A powerful search language used to filter and find issues based on specific criteria.

#### **23\. Dashboard**

A customizable panel that displays reports, charts, and key project information.

#### **24\. Gadgets**

Widgets used in dashboards to show issue statistics, progress, and reports.

#### **25\. Issue Security**

Controls who can view or modify specific issues in a project.

#### **26\. Roles and Groups**

Defines different access levels for users, such as **Administrators, Developers, and Testers**.

#### **27\. Components vs. Labels**

* **Components** – Defined project sections (e.g., UI, Backend).
    
* **Labels** – Flexible tags that help categorize issues.
    

#### **28\. Automation Rules**

Predefined actions that trigger automatically based on specific conditions (e.g., auto-assigning bugs).

#### **29\. Epics vs. Stories vs. Tasks**

* **Epic** – A large feature that consists of multiple stories.
    
* **Story** – A user requirement that contributes to an epic.
    
* **Task** – A specific piece of work that needs to be completed.
    

#### **30\. Service Desk (JIRA Service Management)**

A feature used for IT support and customer service requests.