
In this video we'll learn about the project for this course.
In this video we'll get a better idea of the scenario for our project.
Set up Jira boards for dev and QA teams, using a Scrum board for dev sprints and a Kanban board for QA, with a single point of contact per issue.
In this video we'll start our project by creating a new agile board.
Create a new column named sent to qa in the jira board using board settings to auto-map a status under the simplified workflow, triggering issues to qa.
In this video we'll create some custom statuses that we'll need for our board.
Build a QA team kanban board from the dev project, filter to show only bugs, and map statuses so 'send to QA' appears in the QA to-do column.
Adjust the 'Done' statuses across dev and QA boards by moving issues through in progress to QA approved, then hide those statuses to keep the boards clean.
In this video we'll take a moment to understand how the teams are set up in our scenario, so we'll have a better idea of how they need to communicate with each other through JIRA.
Automate Jira workflows to auto assign issues between qa and dev; set assignee to Christian when qa sends back and to Josie when dev sends to qa.
Use Jira color cards to visually mark bugs that return from QA as red by applying a custom query like status='QA needs fixes', across dev and QA boards.
In this video we'll finish off the course and say our goodbyes.
This Team workflows in JIRA course is intended to give you some tips, tricks and techniques you can use right away to work better in JIRA. We'll use a project-based approach to build a workflow that allows a dev team to send issues to a QA team and then have the QA team send them back through JIRA's agile boards.
Along the way, we'll learn about many of JIRA's features including agile boards, filters, permissions, workflows, schemes, and many more.
This course is perfect for JIRA administrators and anyone who's familiar with JIRA but wants to learn some new tips and tricks for building team workflows in JIRA.