Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering JIRA 7

You're reading from   Mastering JIRA 7 Become an expert at using JIRA 7 through this one-stop guide!

Arrow left icon
Product type Paperback
Published in Oct 2016
Publisher Packt
ISBN-13 9781786466860
Length 450 pages
Edition 2nd Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Ravi Sagar Ravi Sagar
Author Profile Icon Ravi Sagar
Ravi Sagar
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Preface 1. Planning Your JIRA Installation 2. Searching in JIRA FREE CHAPTER 3. Reporting – Using Charts to Visualize the Data 4. Customizing JIRA for Test Management 5. Understanding Zephyr and its Features 6. Sample Implementation of Use Cases 7. User Management, Groups, and Project Roles 8. Configuring JIRA User Directories to Connect with LDAP, Crowd, and JIRA User Server 9. JIRA Add-On Development and Leveraging the REST API 10. Importing and Exporting Data in JIRA and Migrating Configuration 11. Working with Agile Boards in JIRA Software 12. JIRA Administration with ScriptRunner and the CLI Add-on 13. Database Access 14. Customizing Look, Feel, and Behavior 15. Implementing JIRA Service Desk 16. Integrating JIRA with Common Atlassian Applications and Other Tools 17. JIRA Best Practices 18. Troubleshooting JIRA

Setting up JIRA for bug tracking


JIRA can be used out-of-the-box for bug tracking. It comes with a default issue type called Bug, along with other issue types. However, you may be required to make certain changes in the default configurations in the future, and it is a good idea to create custom schemes even for bug tracking. Of course, we will copy the default schemes and make changes in the copied configurations.

Issue types

The following are the issue types for bug tracking:

Scheme name

Issue types

Remarks

Default Issue Type Scheme

Improvement

Bug

New Feature

New User Request

Sub-task

There's no need to create new issue types or new schemes here

Workflow

We will use a custom workflow for the Bug issue type; it will be used to store project requirements; for rest of the issue types, the default JIRA workflow will be used.

The following is the workflow for bug tracking:

From

To

Remarks

Open

Confirmed

Resolved

Closed

Waiting for Client

  • Condition: Only the assignee can...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at ₹800/month. Cancel anytime