Book Image

Jira 8 Essentials - Fifth Edition

By : Patrick Li
Book Image

Jira 8 Essentials - Fifth Edition

By: Patrick Li

Overview of this book

Atlassian Jira enables effective bug tracking for your software and mobile applications and provides tools to track and manage tasks for your projects. Jira Essentials is a comprehensive guide, now updated to Jira 8 to include enhanced features such as updates to Scrum and Kanban UI, additional search capabilities, and changes to Jira Service Desk. The book starts by explaining how to plan and set up a new Jira 8 instance from scratch before getting you acquainted with key features such as emails, workflows, business processes, and much more. You'll then understand Jira's data hierarchy and how to design and work with projects. Since Jira is used for issue management, this book delves into the different issues that can arise in your projects. You’ll explore fields, including custom fields, and learn to use them for more effective data collection. You’ll create new screens from scratch and customize them to suit your requirements. The book also covers workflows and business processes, and guides you in setting up incoming and outgoing mail servers. Toward the end, you’ll study Jira's security model and Jira Service Desk, which allows you to run Jira as a support portal. By the end of this Jira book, you will be able to implement Jira 8 in your projects with ease.
Table of Contents (16 chapters)
Free Chapter
1
Section 1: Introduction to Jira 8
5
Section 2: Jira 8 in Action
11
Section 3: Advanced Jira 8

Running a project with Kanban

Now that we have seen how to run projects with Scrum, it is time to take a look at the other agile methodology Jira Software supports—Kanban. Compared to Scrum, Kanban is a much simpler methodology. Unlike Scrum, which has a backlog and requires the team to prioritize and plan their delivery in sprints, Kanban focuses purely on the execution and measurement of throughput.

In Jira, a typical Kanban board will have the following differences compared to a SCRUM board:

  • There is no backlog view by default. Since Kanban does not have a sprint-planning phase, your board acts as the backlog. We will see how to enable backlog for Kanban in later sections.
  • There are no active sprints. The idea behind Kanban is that you have a continuous flow of work.
  • Scrum and Kanban have different type of reports that are specifically designed for each of the methodologies...