Basic configuration and settings for Jira

Turn from: http://blog.csdn.net/marising/archive/2008/11/18/3327528.aspx

Recently, the company used Jira to do feature management, project management, defect management tools. So I groped myself for a jira setting. Look at the Properties page for project first:
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 notifications from this project would come from the default address
Project Category:None

What you need to set up are:
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
The default is divided into feature (features), improvement (improvements), bugs (Bugs), Task (tasks), covering several aspects of project management, but I think improvement dispensable, can be replaced by several others. Characteristics, refers to the new increase in demand, generally need to undergo research and review stage. A task generally refers to the tasks of designing and coding. A bug is a flaw found during the testing process.

2.Priority Priority
blocker, a problem that causes testing or development to be impossible. such as database access to the public library, or communication components problem, or login components have problems, and so on.
Critical, the main module crashes, memory leaks, data loss and other serious problems.
Major, major features are problematic
Minor, minor features are problematic
Trivial, minor problems, such as the ease of use of the interface, aesthetics, and other insignificant flaws
General project is divided into 5 level is enough, as if priority is for bugs, but feature is also to be used, feature high priority, it is necessary to achieve as soon as possible.

3.Statuses status
Workflow mainly divided into status and transition. The statues defined here are available for global use, so the absence of any state is defined here. I add a disputed (disputed) state, in the bug process, if the developer found that the defect is not a defect, is repeated, can not reproduce, etc., can submit a defect disputed status, the project manager to decide.

4.Resolution Solution
Fix fix
Wont fix don't want to fix, generally need to choose this bar.
Duplicate, repetition of defects
Incomplete, not described clearly
Cannot reproduce, appeared once, and then could not reproduce
Invalid, not verified, is a false flaw.
Later, later version repair

5.Custom Fields custom Field
There are some fields by default, but it doesn't seem to be enough to add bugcategory and Bugsource as well as Featurecategoy and Featuresource fields, indicating the type of bug (System, program logic, data format, Interface bugs) and the source of the bug (internal testing, integration testing, user feedback, etc.).

1.issuetype,issue type
2.Summary, outlining
3.Affects version, affecting version
4.component,project The following component
5. Bugcategory, Defect type (custom field)
6.BugSource, defect source (custom field)
7.Priority, Priority
8.Assignee, developer
9.Reporter, reporting person
10.Time tracking, time estimate
11.Due date, overdue date
12.Fix version, fix version
13.Resolution, Solution
14.Description, Description
15.Attachment, Attachment

6.Field Configuration
Defines whether a field is displayed, whether it must be a property. In different Issuetype, the properties of the field are not the same.

7.Field Configuration Scheme
Establish an association between Issuetype and field Configuration, preferably each type to create a field Configuration

8.Screens View
There are many kinds of sceen, which are divided into two kinds. One is issue creation, edit, view view, and the other is Workflow view, in the process of the process, you need to fill out some values, so you need to design screen. Note that the Fix version field, which can only be filled out in subsequent processes, cannot be filled out at creation time, which means that even if you have added to screen, creating issue you can't see.

9.Sceen Scheme
According to Issuetype to establish scheme, such as bugs, there are create Issue,edit Issue,view Issue three categories, respectively, corresponding to a screen is enough.

10.Issue Type Screen Scheme
is to create a new Issuetype and screen scheme, such as building a XXX Project issue type screen scheme, and then the bug corresponds to the bug screen scheme in 9.

11.Workflows Work Flow

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

The bug general process is

Open->start progress-> inProgress -> Resolve bugs-> resolved-> Close Bugs-> Closed

Bugs other processes are

Open -> dispute Bug-> disputed -> Terminate-> terminated

The black letter is the state, the other is the action

Step Name (ID)	linked Status	transitions (ID)
Open (1)	Open	Start Progress (11) >> in Progress Dispute Bugs (31) >> disputed
In Progress (2)	In Progress	Stop Progress (41) >> Open Resolve Bugs (51) >> resolved Dispute Bugs (81) >> disputed
reopened (3)	Reopened	Start Progress (61) >> in Progress Dispute Bugs (71) >> disputed
Resolved (4)	Resolved	Close Bug (91) >> Closed Reopen Bugs (121) >> reopened
Closed (5)	Closed	Reopen Bugs (111) >> reopened
disputed (6)	Disputed	Reopen Bugs (131) >> reopened Terminate Bugs (141) >> terminated
terminated (7)	Terminated	Reopen Bugs (151) >> reopened

Look at an example of a transition
Conditions: You can choose who has permission to handle
Post functions: Operations after migration, changes to status/fields, and so on.
Transition View: Views at the time of migration, allowing the operator to fill in some fields. Reference 8


12.Workflow schemes
Issue the corresponding relationship between type and workflow.

13.Permission Schemes permission settings
Permissions are set where the user Browser,group Browser,project role brower, and the following two represent different groups of users.
In permission scheme, you can set permissions on a number of items that are fed back into the use process. assignable User permissions, you decide to create issue specify assignee permissions.

14.Notification Schemes Notification Settings
Look at the set yourself, it is better not to be too frequent, otherwise very annoying.