Practical JIRA Workflows and Boards for Scrum Projects

Explore how Jira workflows define processes with statuses and transitions, and how workflow schemes map issue types to projects for transparent, real-time team workflows.

Sketch a flow design for two Jira workflows, tasks/epics and stories/bugs, with to do, in progress, done, ready for qa, and qa in progress, plus transitions, screens, and resolutions.

Learn to create a Jira workflow scheme, assign stories and bugs to a qa workflow and tasks and epics to a non-qa workflow, and associate the scheme with a project.

Discover how Jira statuses define workflow stages, create and categorize statuses like to do, in progress, and done, and tailor workflows with copies and transitions for scrum projects.

Define transitions that move an issue between statuses, such as start planning, start building, and finish, enabling linear or non-linear Jira workflows and control through conditions, validators, and triggers.

Configure a Jira transition screen to collect extra information during transitions in a workflow and capture notes in comments when moving an issue to in progress.

Learn how Jira resolutions explain why an issue is completed, distinct from statuses, and how to set and customize resolutions during the finish transition.

Use post functions to perform processing after a transition. Apply essential post functions in order: set status, add a comment, update history, re-index, and fire events.

Explore JIRA workflow properties, including transition properties to customize transitions and status properties to restrict actions, such as editing once an issue moves to Done.

Configure triggers in JIRA workflows to automatically transition issues when events occur in Bitbucket, GitHub, Crucible, or Fisheye, and push branches with the issue key to wake the trigger.

Explore how conditions govern Jira transitions, including grouping and user-based rules. Learn to clone workflows and configure statuses like ready for QA and QA in progress, with finish to done.

Explore how transition validators enforce criteria in Jira workflows, including field and date checks, and how to require a comment for done transitions in the qa workflow.

Explore how Jira boards provide flexible, customizable views of work in Scrum and Kanban. Aggregate issues across projects, plan, monitor, and import CSV to populate boards and enable story points.

Discover how JIRA boards organize work using the default WB board, review backlog, active sprints, roadmap, and reports, and switch between multiple boards.

Explore backlog grooming in Jira, prioritize and split issues, use filters and quick actions to manage versions and epics, and plan sprints with explicit goals.

Explore active sprints and backlog on a Jira board, where columns map statuses, transitions govern moves, and dragging issue cards align with the sprint goal 'user authentication'.

Configure Jira boards by setting general settings and filters, create three boards (Full Board, Mini Board, Tasks Board), and use JQL to show only tasks and high-priority issues.

Configure Jira boards by creating quick filters, applying color rules for priorities, and customizing card layouts; set story point estimates, time tracking, working days, and enable the roadmap.

Clone the existing tasks board to quickly create two new boards, Full board and Mini board, carrying over all prior configurations. Update the copied boards by creating and selecting the WB-Full-Mini filter, and share it with the Workflows and Boards project so both boards can access all issues.

Configure full and mini boards in Jira by adding columns and mapping statuses such as Ready for QA and QA in progress, and group issues by epics with swimlanes.

Explore how Jira boards and workflows merge on the active sprints screen, progressing issues from to do into in progress, ready for qa, and done across a two-week sprint.

Create a kanban board, compare it with the scrum board, and configure kanban backlog with columns for two qa statuses and no sprints.

Explore how Jira roadmaps visualize epic timelines and progress within sprints, with drag-and-drop prioritization, timescales, and inline editing, noting that epics contain stories, tasks, and bugs.

Explore how Jira reports provide real-time insights into progress, efficiency, and scope, and learn to use burndown, burnup, sprint, velocity, and cumulative workflow diagrams.

Explore how burndown charts in JIRA predict sprint completion by tracking remaining work, scope changes, and the red line against the gray guideline in reports.

Explore how the burnup chart tracks sprint progress by completed work, with red scope and green progress lines, and how scope changes separate from progress.

Explore how the sprint report and velocity chart summarize sprint progress with burndown charts and issue status, including completed and incomplete items, outside sprint, and removed items, for retrospectives.

learn how jira's velocity chart measures team capacity across completed sprints, using committed and completed points to forecast future sprint planning and set realistic baselines.

Master the cumulative flow diagram, an area chart of issue statuses over time, to spot bottlenecks in scrum projects with sprints or kanban projects without sprints.

Discover how to use the Jira mobile app boards, backlog, and roadmap. Learn drag-and-drop cards, sprint actions, and filters on mobile, not a replacement for web.

Learn how to use Jira workflows in boards and apply them to Scrum projects, and provide feedback to improve future courses.