Use JIRA to build an enterprise issue tracking system. PART1)

JIRA is a good business problem tracking tool developed by Atlassian, Australia. It can track and manage various types of problems, including defects, demand changes, and review records. When I selected the defect tracking tool, I tried JIRA for a while and I personally felt very good. Based on the problems encountered during the trial and my personal experience, I sorted out the trial records.

   This article mainly introduces JIRA customization, and describes how to customize JIRA based on the company's actual needs, suitable for administrators. The basic usage of JIRA is similar to that of common defect tracking tools.

   You can go to the JIRA Official WebsiteAt www.atlassian.com/jira, the detailed information of jirais is displayed.

1. Background

   Before using JIRA, the company uses Bugzilla as a defect tracking tool. In the early stages of use, Bugzilla did play a certain role, but with the company's need to strengthen project management, Bugzilla was not enough.

   When the project team uses Bugzilla, there are several problems:

● The project team should record different types of problems, such as issues found in Task Assignment and review, requirement change records, and defects. Although these types of problems can be considered as defect records in Bugzilla, this obfuscated the defect tracking process because the processing processes for these different types of problems are different, however, you cannot customize multiple problem tracking procedures in the system in Bugzilla.

● The Project Manager cannot record the expected repair completion time of the defect

● Project Managers cannot allocate or edit defects in batches

● It is impossible to record the workload of developers to handle defects, and the workload is not compared.

● Developers cannot quickly and intuitively clearly identify the defects assigned to themselves, and do not visually display the defects being processed.

● The tester does not know the expected version of the defect fix, resulting in unclear scope of the defect regression.

● Upgrade is inconvenient and costly.

● Other details, such as unfriendly interfaces and inability to upload attachments.

2                 Introduction

   Tracking and managing problems (such as defects, new features, demand changes, and QA audits) presented during the project process is an important task of project management, but few teams can do well. Although JIRA is a problem tracking system, it can become a project management software after a slight transformation. It is an application system for problem tracking and Project Management. It aims to make the problems presented during the project process easy.

     JIRA has the following features:

● Manage defects, new features, tasks, improvements, or any other problems

● Clean and powerful user interfaces facilitate understanding of commercial and technical users

● Workflow Customization

● Full-text search and powerful filters (customizable, retainable, shared, and predefined filters)

● Customizable workbench and real-time statistics

● Enterprise-level permissions and Security Control

● Convenient extension and integration with other systems (including email, RSS, Excel, XML, and source code control tools)

● Very high configuration of notification options

● Run on almost all hardware, operating systems, and database platforms

   JIRA can provide the required information according to your needs. The following uses defects as an example to describe the information that each role member can obtain in Jira and what they can do.

● Management Personnel-learn about the project status based on the statistical results of defect data

  ■ View the overall problem distribution of the project

  ■ View the overall problem workload and progress of the project

  ■ View the development workload of a developer in different projects

  ■ View the workload of a specific version of the project and the defects and remaining workload of each user

● Project Manager-evaluate and allocate Defects

  ■ View issues assigned to me

  ■ View the details of a problem

  ■ Allocation problems

  ■ Fill in the expected troubleshooting time and estimated workload for fixing the problem

● Developers -- handle defects and submit workload records

  ■ Accept the problem and prepare to start handling the problem

  ■ Fill in the handling information on the system after troubleshooting

 

  ■ Fill in handling information

  ■ After completing the information processing, prepare to fill in the workload involved in troubleshooting

  ■ Fill in the workload for troubleshooting

● Tester-Quickly submit defects and track defects

  ■ Submit questions

  ■ Fill in question details

  ■ View different problems based on different filtering conditions and prepare to track and handle problems

  ■ Query results listed based on different filtering Conditions

  ■ Verify the problem handling status and select different operations based on different workflow nodes

3 Install

   Compared with Bugzilla, JIRA has an outstanding advantage: you do not need to spend hours or days building your problem tracking system, JIRA can be built and run on your system within 30 seconds. The following describes how to install JIRA.

1.Run the startup. bat file in the/bin directory to go to the installation page.

2.Select an index directory And enter licence to perform the next step.

3.Enter the created administrator information and perform the next step.

4.On the Mail Server Page, other information is easily described. It is emphasized that in the SMTP server input box, enter the IP address, namely: 192.168.168.116 (internal mailbox), the user name is the internal mailbox User Name (such as: xfshen@xx.com), execute the next step

5.Complete installation