Basic configurations and settings of Jira

Recently, the company used Jira as a tool for feature management, project management, and defect management. Therefore, I explored the Jira settings myself. First, let's take a look at the properties page of the project:
Key:Xxx
URL:No URL
Project Team:
Project Lead: Li Haibo
Default assignee: project lead
Project roles:
Issue type scheme:Default issue type Scheme
Notification Scheme:Xxx Notification Scheme
Permission scheme:Xxx permission Scheme
Issue Security Scheme:Xxx Security
Field configuration scheme:Xxx configuration Scheme
Issue Type Screen scheme:XXX project issue Type Screen Scheme
Workflow scheme:Xxx Workflow
CVS modules:None
Mail Configuration:Mail communications from this project will come from the default address
Project category:None

You must set the following parameters:
Issue type Scheme
Notification Scheme
Permission Scheme
Issue Security Scheme
Field configuration Scheme
Issue Type Screen Scheme
Workflow Scheme
The last three items are the most troublesome.

1. Issue type
By default, it can be divided into feature, improvement, bug, and task, covering several aspects of project management. However, I think improvement is dispensable, it can be replaced by several others. Feature refers to the new demand, which generally needs to be investigated and reviewed. A task is generally a task designed and encoded. Bugs are defects found during testing.

2. Priority priority
BlockerIs a problem that causes testing or development failure. For example, there are problems with the public database accessed by the database, communication components, or login components.
CriticalIt refers to major module crashes, memory leaks, data loss, and other serious problems.
Major, Main function problems
Minor, Secondary function problems
TrivialMinor problems, such as ease of use of the interface, appearance, and other minor defects
Generally, it is enough to divide the project into five levels. It seems that the priority is for bugs, but feature is also needed. The priority of feature is high and must be implemented as soon as possible.

3. statuses status
Workflow mainly includes status and transition. The statues defined here can be used globally. Therefore, it is necessary to define the missing status here. I have added a disputed (controversial) status. In the bug process, if a developer finds that a defect is not a defect, it is a duplicate and cannot be reproduced, the developer can submit the defect not disputed status, it is determined by the Project Manager.

4. Resolution Solution
Fix
Wont fix does not want to be repaired. You need to select this one.
Duplicate, repeated Defects
Incomplete, not clearly described
Cannot reproduce, which appears once and cannot be reproduced later
Invalid, unverified, is a false Defect
Later, which will be restored later

5. Custom fields of custom Fields
There are some fields by default, but it does not seem to be enough. You can add bugcategory, bugsource, featurecategoy, and featuresource fields to specify the bug category (system, program logic, data format, interface, and other bugs) and bug source (internal test, integration test, user feedback, etc ).

1. issuetype, issue type
2. Summary, summary
3. affects version, affected version
4. Component: components under the project
5. bugcategory, defect type (Custom field)
6. bugsource, defect source (Custom field)
7. Priority, priority
8. assignee, developer
9. Reporter, Reporter
10. time tracking, Time Estimation
11. due date, expiration date
12. Fix version, fix version
13. Resolution, Solution
14. Description, description
15. Attachment, Attachment

6. Field Configuration
Defines whether the field is displayed and whether the attribute is required. In different issuetype, the field attributes are different.

7. Field configuration Scheme
Establish an association between issuetype and field configuration. It is best to create a field configuration for each type.

8. Screens View
There are many types of sceen, which are roughly divided into two types. One is the creation, editing, and view of issue, and the other is the view of workflow. Some values need to be filled during the process, so screen needs to be designed. Note that the fix version field can only be entered in the subsequent process and cannot be filled during creation. That is to say, even if you add it to screen, you will not be able to see how to create an issue.

9. sceen Scheme
Scheme is created based on issuetype. For example, if a bug occurs, create issue, edit issue, and view issue are created. It is sufficient to correspond to a screen.

10. Issue Type Screen Scheme
Is to create a ing between issuetype and screen scheme. For example, to create a XXX project issue Type Screen scheme, and then the bug corresponds to the bug screen scheme in 9.

11. workflows Workflow

The following list shows the running status and steps of a process.

 

The general bug process is

Open-> Start progress->In progress-> Resolve bug->Resolved->Close bug->Closed

Other bug procedures are:

Open-> Dispute bug->Disputed-> Terminate->Terminated

 

The black text is the status, and the other is the action.

 

Step name(ID)	Linked status	Transitions (ID)
Open(1)	Open	Start progress (11) > In progress Dispute bug (31) > Disputed
In progress(2)	In progress	Stop progress (41) > Open Resolve bug (51) > Resolved Dispute bug (81) > Disputed
Reopened(3)	Reopened	Start progress (61) > In progress Dispute bug (71) > Disputed
Resolved(4)	Resolved	Close bug (91) > Closed Reopen bug (121) > Reopened
Closed(5)	Closed	Reopen bug (111) > Reopened
Disputed(6)	Disputed	Reopen bug (131) > Reopened Terminate bug (141) > Terminated
Terminated(7)	Terminated	Reopen bug (151) > Reopened

 

Let's look at a transition example.
Conditions: You can select who has the permission to process
Post functions: post-migration operations, status/field modifications, etc.
Transition view: the view at the time of migration, which allows the operator to fill in some fields. Reference 8

12. workflow schemes
The relationship between issue type and workflow.

13. Permission schemes permission settings
The permission settings include user browser, group browser, and project role Brower. The latter two indicate different user groups.
In permission scheme, you can set permissions for many items, which will be reported during use.Assignable userThe permission of the specified assignee is determined when the issue is created.

14. notification schemes notification settings
Let's take a look at the settings. It is best not to be too frequent, otherwise it will be annoying.

 

JIRA graphical plug-in