Book Image

JIRA 7 Essentials - Fourth Edition

By : Patrick Li
Book Image

JIRA 7 Essentials - Fourth Edition

By: Patrick Li

Overview of this book

Atlassian JIRA is an enterprise-issue tracker system. One of its key strengths is its ability to adapt to the needs of the organization, ranging from building Atlassian application interfaces to providing a platform for add-ons to extend JIRA's capabilities. JIRA 7 Essentials, now in its fourth edition, provides a comprehensive explanation covering all major components of JIRA 7, which includes JIRA Software, JIRA Core, and JIRA Service Works. The book starts by explaining how to plan and set up a new JIRA 7 instance from scratch for production use before moving on to the more key features such as e-mails, workflows, business processes, and so on. Then you will understand JIRA's data hierarchy and how to design and work with projects in JIRA. Issues being the corner stone of using JIRA, you will gain a deep understanding of issues and their purpose. Then you will be introduced to fields and how to use custom fields for more effective data collections. You will then learn to create new screens from scratch and customize it to suit your needs. The book then covers workflows and business processes, and you will also be able to set up both incoming and outgoing mail servers to work with e-mails. Towards the end, we explain JIRA's security model and introduce you to one of JIRA’s new add-ons: JIRA Service Desk, which allows you to run JIRA as a computer support portal.
Table of Contents (17 chapters)
JIRA 7 Essentials - Fourth Edition
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface

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. Since Kanban does not have a sprint-planning phase, your board acts as the backlog.

  • There are not active sprints. The idea behind Kanban is that you have a continuous flow of work.

  • Columns can have minimum and maximum constraints.

  • Columns will be highlighted if the constraints are violated. As shown in the following screenshot, both the Selected for Development and In Progress columns are highlighted due to constraint violation:

Creating a Kanban project

The first step to work...