JIRA - Workflow

Jira - Understanding Workflows

In Jira, a workflow defines the sequence of steps or statuses an issue moves through during its lifecycle, from creation to completion. It’s a fundamental concept for tracking progress and managing work. Each status represents a specific stage in the issue’s journey (e.g., ‘To Do’, ‘In Progress’, ‘Done’).

A transition is the link between two statuses, representing the action taken to move an issue from one status to another. For an issue to change its status, a defined transition must exist. Think of a transition as the ‘verb’ (e.g., ‘Start Progress’) and the status as the ‘state’ (e.g., ‘In Progress’).

Core Workflow Concepts

A typical, simplified workflow might involve the following stages:

• Open / To Do: The issue has been created and is awaiting action. It can be assigned to a team member.
• In Progress: The assigned team member has actively started working on the issue.
• Under Review / In QA: The work is completed and is awaiting review or quality assurance testing.
• Resolved / Done: All work associated with the issue is complete, and it has passed any necessary reviews or tests. A ‘resolution’ (e.g., ‘Fixed’, ‘Completed’, ‘Won’t Fix’) is typically set at this stage.
• Reopened: The issue was previously resolved, but further work is required, perhaps due to a failed review or new information.
• Closed: The issue is considered fully complete and no further action is expected. Some workflows might combine ‘Resolved’ and ‘Closed’ into a single ‘Done’ status.

While this resembles a defect lifecycle, Jira workflows are highly versatile and can be configured to model various processes for different issue types like tasks, stories, epics, or service requests.

A textual representation of a common workflow could be: TO DO → IN PROGRESS → IN REVIEW → DONE. An issue might also transition from DONE → REOPENED if it needs further attention, and then back to IN PROGRESS.

Modern Jira allows for highly customizable workflows. Administrators can define unique statuses, transitions, and even conditions, validators, and post-functions for transitions to tailor the workflow to specific project needs or issue types. Workflows are associated with projects and issue types through ‘Workflow Schemes’.

Transitions are typically one-way. If an issue needs to move back and forth between two statuses (e.g., ‘In Progress’ and ‘Blocked’), separate transitions must be defined for each direction.

Practical Application: Agile Development

In Agile methodologies like Scrum or Kanban, workflows are visualized on boards. Each column on the board often corresponds to a status in the Jira workflow, allowing teams to track the flow of work, identify bottlenecks, and manage sprint commitments effectively.

Automation in Workflows

Jira allows for automation rules to be triggered by workflow transitions. For example, when an issue transitions to ‘Resolved’, an automation rule could:

• Automatically assign the issue to a QA engineer.
• Notify the reporter that the issue is ready for verification.
• Update a related field.

Common Learning Point: It’s important to distinguish between a ‘status’ (the current stage of an issue) and a ‘resolution’ (the reason an issue is considered complete, e.g., ‘Fixed’, ‘Duplicate’, ‘Won’t Do’). Resolutions are typically set when an issue transitions to a terminal status like ‘Done’ or ‘Closed’.

For more detailed information on configuring workflows, refer to the official Atlassian Jira documentation on workflows and workflow schemes.