Khadija Daruwala

Posted on Aug 6

Jira Without the Jargon: A Developer's Guide to Actually Using It

#jira #productivity #agile #softwaredevelopment

TL;DR: Jira doesn't have to be scary. Here's a clear, no-fluff guide to the concepts that actually matter.

When I first started using Jira, it felt like walking into a spaceship cockpit. There were boards, backlogs, epics, sprints, JQL, and a dozen other terms I didn't understand.

But after using it daily for a while, I realized Jira is actually pretty simple once you know what matters.

So here's my guide-a clear, plain-English walkthrough of how I use Jira as a developer. No corporate jargon. No "Agile transformation" talk. Just the stuff that helps you ship work without losing your mind.

What Is Jira?

Jira is a project management and issue tracking tool developed by Atlassian. It helps teams plan, track, and manage work throughout the software development lifecycle.

In simple terms: it's where your team writes down what needs to be done, who's doing it, and when it's done.

Jira is used for:

Software and hardware development
Agile methodologies (Scrum, Kanban)
Bug tracking and task management
Release and sprint planning

Think of it like a to-do list on steroids-except it's for entire teams and comes with boards, filters, and reports.

Project Types: Team vs Company

When you create a project in Jira, you'll see two main options: Team-managed and Company-managed.

Team-managed Project

A Team-managed project gives individual teams full control over how their project is configured.

Characteristics:

Easy to set up-no Jira administrator required
Each project has its own configuration
Workflows, issue types, and fields can be customized per project
Ideal for small teams or pilot projects

Advantages:

Fast onboarding
Flexible and adaptable
Independent from other projects

Disadvantages:

Inconsistent configurations across teams
Limited advanced features (e.g., no Components, limited custom fields)
Harder to scale or standardize across an organization

Best for: Small teams wanting full control over their workflow without admin dependency.

Company-managed Project

Company-managed projects are centrally administered by Jira administrators.

Characteristics:

Shared workflows, issue types, screens, and permissions
Configured and maintained by Jira administrators
Supports advanced customization and cross-project standardization

Advantages:

Consistent processes across teams
Easier to scale and govern
Full feature set (Components, advanced permissions, roadmaps)
Recommended for medium to large organizations

Disadvantages:

Requires administrator involvement for changes
Less flexible for individual teams

Best for: Organizations needing standardized workflows, advanced permissions, or cross-team collaboration.

Feature	Team-managed	Company-managed
Setup	Self-service by team	Requires Jira admin
Configuration	Independent per project	Shared across projects
Flexibility	High	Medium (standardized)
Advanced Features	Limited	Full support
Best For	Small, autonomous teams	Medium/large orgs

Pro tip: Don't overthink this. Just pick the one your team uses and move on.

Boards: Where Work Lives

A board is a visual representation of work, showing tasks as they move through different stages.

Example workflow:

To Do → In Progress → Code Review → Testing → Done

Boards help teams monitor progress, identify bottlenecks, and maintain flow.

Jira has two main board types:

Kanban Board

Kanban is a continuous workflow with no sprints. Work moves continuously from left to right.

Workflow:

Backlog → To Do → In Progress → Review → Testing → Done

Best for:

Maintenance and support teams
DevOps and IIoT projects
Continuous delivery environments
Hardware engineering with ongoing tasks

Kanban emphasizes limiting work in progress (WIP) and optimizing flow efficiency.

Scrum Board

Scrum organizes work into fixed-length sprints.

Typical sprint duration: 1–3 weeks

Sprint cycle:

Sprint Planning → Development → Testing → Sprint Review → Retrospective

Best for:

Feature development
Teams working in iterative cycles
Product teams with clear sprint goals

Scrum boards display sprint backlog, active sprint, and completed work.

Backlog: Your "Someday" List

The backlog is a prioritized list of future work items not currently in progress.

Typical backlog items:

New features (Stories)
Bugs
Technical debt
Improvements
Research or discovery tasks

The Product Owner or Project Manager owns backlog prioritization, ensuring the team works on the highest-value items first.

Issues: The Building Blocks

An issue is the smallest unit of work in Jira. Think of it like a task card.

Core fields:

Issue Type
Summary
Description
Status
Assignee
Priority

Optional fields:

Labels
Components
Fix Version
Epic Link
Story Points
Attachments

Issue Types: What's What

Epic

An Epic is a large body of work that can be broken into multiple Stories.

Example: Customer Portal

Epics provide a high-level container for tracking related work across sprints.

Story

A Story represents a user-facing feature, often written in user-story format.

Example:
As a customer, I want to reset my password so that I can regain access.

Stories are small enough to be completed within a sprint.

Task

A Task is general work not tied to a user story.

Example: Upgrade Docker version

Tasks can be technical, administrative, or operational.

Bug

A Bug represents a defect or issue in the system.

Example: Temperature sensor displays incorrect values.

Bugs are prioritized based on severity and impact.

Sub-task

A Sub-task is a smaller piece of work within a parent issue (Story, Task, or Bug).

Example:
Story: Implement Login
Sub-task: Create Login Button

Sub-tasks help break down complex work into manageable units.

Workflows: How Work Moves

A workflow defines the lifecycle of an issue—from creation to completion.

Typical workflow states:

To Do → In Progress → Code Review → Testing → Done

Workflows can include:

Statuses: To Do, In Progress, Done
Transitions: Move issue from one status to another
Conditions: Rules that control who can transition an issue
Validators: Checks before a transition is allowed
Post-functions: Automated actions after a transition (e.g., send notification)

Company-managed projects support advanced workflow customization, while team-managed projects offer simpler, per-project workflows.

Sprint Planning

Sprint planning is a Scrum ceremony where the team selects backlog items for the upcoming sprint.

Key activities:

Review prioritized backlog
Estimate effort (e.g., story points)
Commit to sprint goals
Assign issues to team members

Sprint duration: Typically 1–3 weeks, depending on team velocity and project needs.

Sprints help teams deliver value incrementally and maintain a predictable cadence.

Roadmaps: The Big Picture

Roadmaps (or Timelines) provide a long-term, strategic view of work.

They answer:

What are we building?
When will it be delivered?
What dependencies exist?
What is the current progress?

Use cases:

Quarterly planning
Product releases
Hardware and software milestones
Cross-team dependency tracking

Roadmaps are especially useful in company-managed projects with full feature support.

Filters & JQL: Finding Stuff Fast

Filters

A filter is a saved search that displays issues matching specific criteria.

Examples:

My Open Issues
High Priority Bugs
Sprint 10 Tasks

Filters can be shared with teams and used in dashboards.

JQL (Jira Query Language)

JQL is Jira's query language for searching issues with precision.

Common examples:

assignee = currentUser()

Issues assigned to me.

status = "In Progress"

All issues currently in progress.

project = APP

All issues in the APP project.

priority = High

High-priority issues.

labels = backend

Issues tagged with the "backend" label.

assignee = currentUser() AND status != Done

My open, incomplete issues.

JQL supports complex queries using AND, OR, NOT, and field operators.

Dashboards: Your Project Health Check

Dashboards provide a high-level overview of project health using configurable gadgets.

Common gadgets:

Assigned to Me
Pie Chart (by status, priority, assignee)
Created vs Resolved
Sprint Burndown
Activity Stream
Filter Results

Dashboards help managers and developers quickly assess progress, identify bottlenecks, and track team performance.

Labels vs Components

Both are used to categorize issues, but serve different purposes.

Feature	Labels	Components
Purpose	Flexible tagging	Structural categorization
Scope	Free-form, ad-hoc	Predefined by project
Availability	Team & Company-managed	Company-managed only
Use Case	Cross-project tagging	Module or feature ownership
Example	`backend`, `urgent`, `refactor`	`API`, `UI`, `Database`

Labels are informal and can be created on the fly.

Components are formal, often tied to teams or code modules, and require admin setup.

Versions & Releases

Versions (or Fix Versions) represent planned releases or milestones.

Use cases:

Track which issues are included in a release
Generate release notes
Monitor progress toward a version

Example:

Version: v2.1.0
Issues with Fix Version = v2.1.0 are part of that release.

Releases can be scheduled, and progress tracked via version reports.

Keyboard Shortcuts

Jira supports keyboard shortcuts to speed up navigation (press ? in Jira to view all).

Common shortcuts:

c — Create issue
/ — Search (quick search)
g + i — Go to Issues
g + b — Go to Boards
g + d — Go to Dashboards
e — Edit issue
m — Move issue
a — Assign issue
l — Add label

Enable keyboard shortcuts in your profile settings for faster workflow.

Quick Tips

Write clear, concise issue summaries.
Keep descriptions complete but brief.
Use labels consistently across the team.
Link related issues (e.g., blocks, is blocked by).
Update issue status regularly to reflect real progress.
Avoid duplicate issues—search before creating.
Use dashboards and filters to monitor progress.
Create reusable JQL filters for common queries.

That's It

Jira isn't perfect, but it's a solid tool once you know the basics. Start simple, keep your workflow clean, and focus on shipping work.

You don't need to be a Jira expert to be productive. You just need to know enough to track your work, collaborate with your team, and ship stuff.

Now go create your first issue and move it to "Done." That's the real win.

Enjoyed this? Drop a comment below or share it with someone who's just starting with Jira. 🚀

DEV Community