Skip to content
Tutorials Center
My learning

Topics

Lesson 34 of 41 ยท Tools and Reporting

Jira Workflows and Issue Tracking

Learn how Jira organizes work: issue types, workflows, boards, sprints, components, epics, filters and JQL, with a runnable Python workflow and query simulation.

Jira, from Atlassian, is the most widely used issue tracker for software and service teams. Even if you never use Jira, the ideas inside it appear in every serious tracker: typed work items, a workflow with statuses and transitions, boards, filters and reports. Learn the concepts once and you can use any of them.

This lesson uses Jira's vocabulary. Jira changes its screens often, so we focus on the concepts and on what you configure, not on button positions. The Jira examples below are descriptions; the Python examples are small stand-ins that model the same ideas so you can run them in your browser.

The building blocks

Jira vocabulary

Project A container for issues and settings.
Issue One unit of work with a key like APP-42.
Workflow Statuses and allowed transitions.
Board Scrum or Kanban view of issues.

Everything else is configuration around these four.

1 / 2
  • Issue types: Epic, Story, Task, Bug and Sub-task by default. Teams add types such as Spike (research), Incident or Change request. Keep the list short.
  • Fields: summary, description, assignee, reporter, priority, labels, components (parts of the product), fix versions (the release), story points, sprint, due date. A good issue states the problem, the acceptance criteria and links.
  • Issue links express relations: blocks, is blocked by, relates to, duplicates. The hierarchy runs epic, story, sub-task.
  • Permissions and roles decide who can create, edit or transition issues.

Workflows: statuses and transitions

A workflow is a small state machine. Each status (To Do, In Progress, In Review, Done) belongs to a category (to do, in progress, done), and a transition moves an issue from one status to another. You can add conditions (who may move it), validators (required fields), and post functions (automatic actions such as setting a resolution).

stateDiagram-v2
  [*] --> ToDo
  ToDo --> InProgress: Start
  InProgress --> InReview: Request review
  InReview --> InProgress: Changes requested
  InReview --> Done: Approve
  InProgress --> Blocked: Blocked
  Blocked --> InProgress: Unblocked
  Done --> [*]

Every allowed move is explicit; anything else is rejected.

Design workflows to match the real process, and keep them short. Each extra status adds clicks and rarely adds insight. The fewer the statuses, the more reliable the data.

Python A workflow as a state machine

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

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The rejected Approve shows why workflows matter: they stop an issue from skipping review.

Boards and sprints

A Scrum board shows the active sprint's issues in columns that map to statuses. A Kanban board shows continuous flow and supports WIP limits per column; Jira highlights a column in red when the limit is exceeded (see Kanban). The backlog view is where you order issues by priority, estimate them, and drag them into a sprint. A roadmap (timeline) shows epics across quarters.

A sprint in Jira has a goal, start and end dates, and committed issues. When it ends, unfinished issues move to the next sprint or back to the backlog (see Scrum for why this should be rare). Jira's built-in reports include the burndown, burnup, velocity chart (see sprint planning and burndown), sprint report, and the cumulative flow diagram, which shows items per status over time and is the quickest way to find a bottleneck.

Finding issues with filters and JQL

Jira Query Language (JQL) is a text query over issue fields. Saved queries are filters, and filters feed boards, dashboards and subscriptions. Examples:

TEXT
project = APP AND status != Done AND assignee = currentUser() ORDER BY priority DESC

project = APP AND issuetype = Bug AND created >= -7d

sprint in openSprints() AND status = "In Review"

fixVersion = "2.3" AND resolution = Unresolved

Core ideas: fields, operators (=, !=, IN, ~ for text), boolean AND/OR, functions (currentUser(), openSprints()) and ORDER BY.

Python A tiny JQL-style query engine

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

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Automation and integrations

Jira automation rules follow a trigger, condition, action pattern: "when an issue moves to Done (trigger), if it has fix version (condition), then post to Slack (action)". Integrations link commits and pull requests to issue keys (put APP-42 in the branch name and commit message), connect to CI/CD, and sync with Confluence for documentation. Use automation to cut routine clicks, for example auto-assigning reviewers or closing stale issues, but keep rules few and named clearly.

Good habits

  • Write issues for the person who will pick them up cold: context, steps to reproduce, acceptance criteria.
  • Keep issues small enough to finish within a sprint.
  • Use labels and components sparingly with agreed names; otherwise they fragment.
  • Groom the backlog: close or archive anything older than six months that nobody will do.
  • Do not use Jira's data to rank people; use it to see flow and blockers.
  • Keep configuration changes under an owner; a workflow edited by everybody breaks.

Other tools such as Azure DevOps, GitHub Projects, YouTrack, Linear and Trello use similar concepts under different names. For more about choosing one, see project management tools.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. In Jira, what controls which status moves an issue may make?

    A workflow defines statuses and the allowed transitions between them, with conditions and validators.
  2. 2. Which issue type usually represents a large goal composed of several stories?

    An epic groups related stories or tasks under a bigger objective.
  3. 3. What does this JQL return: project = APP AND status != Done ORDER BY priority DESC?

    The query filters on project and status and then orders the results.
  4. 4. Which Jira report best reveals a bottleneck by showing issues per status over time?

    A widening band in the cumulative flow diagram shows work piling up in a status.

Summary

  • Jira organizes work as projects, typed issues, workflows and boards; other trackers copy the ideas.
  • A workflow is a state machine of statuses and transitions; keep it short and truthful.
  • Boards show sprints (Scrum) or flow (Kanban); reports include burndown, velocity and cumulative flow.
  • JQL filters issues; automation uses trigger, condition, action.
  • Keep issues small, well described and tidy.

Next: Monitoring and Status Reporting