Book Image

Mastering Redmine - Second Edition

By : ANDRIY LESYUK
Book Image

Mastering Redmine - Second Edition

By: ANDRIY LESYUK

Overview of this book

Redmine is not only one of the popular open source project management applications but also one of the best project hosting and issue tracking solutions. This book is an update of our previous successful edition, Mastering Redmine. This book is a comprehensive guide that will give you a detailed practical understanding on how to effectively manage, monitor and administer complex projects using Redmine. You will get familiar with the concept of Issue Tracking and will get to know why and what makes Redmine one of the best issue trackers. Another main part of Redmine functionality, which is Managing projects shows why this is one of the best applications for project hosting. Furthermore, you will learn more about Redmine rich text formatting syntax, access control and workflow and time Tracking. Towards the end, you will unleash the power of custom fields and guides to show how to customize Redmine without breaking upgrade compatibility. By the end of the book, you will have a deep practical understanding on how to effectively monitor and manage large scale and complex projects using Redmine.
Table of Contents (19 chapters)
Mastering Redmine Second Edition
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Quick Syntax Reference
Index

A practical example


I can't think of any better way to demonstrate the configuration of the workflow than reviewing a real-life practical example. As the Kanban agile methodology is very popular nowadays, let's see how to configure the workflow to satisfy Kanban task rotation practices.

Tip

Before configuring the workflow, it is always helpful to draw a diagram of the issue life cycle.

Kanban does not have any strict requirements for the board and column names, so here we'll use the following issue statuses, which should correspond to column names on the Kanban board (except the New status, which is to be set on issue creation and means to be reviewed):

It is assumed that there is only one tracker and there are three roles: Project manager (who reviews new issues and closes completed ones), Developer, and Tester. The following minimal configuration should be applied in Redmine:

 

NEW

ACCEPTED

IN PROGRESS

TESTING

PASSED

DONE

Project manager

NEW

 

   

PASSED

     

Developer

ACCEPTED...