Good project management tools JIRA

Original: https: //www.jianshu.com/p/8c14b52ce692

Atlassian JIRA is the company's products.

Atlassian company in 2002 in Sydney, Australia, was established to provide for the business process coordination office products , and in December 2015 listed on NASDAQ.
As a SaaS company, we do not hire a sales person, only through word of mouth-acquisition, market capitalization of $ 1 billion level ($ 6.4 billion - March 13, 2017), which also reflects the uniqueness of this product from another angle.

There are five main Atlassian product, respectively, for different markets.

JIRA ( project task management software )
Confluence ( enterprise knowledge management and collaboration software )
BitBucket ( code library )
HipChat ( internal chat / collaboration software )
JIRA Service Desk ( Help Desk Software ).

Atlassian's core products are still JIRA and Confluence , JIRA is widely recognized as the best project management and development management tool , Confluence is considered to be the best enterprise level knowledge management tools used .
Including the US NASA Mars probe designed to use Atlassian, Runkeeper use Atlassian to design fitness applications .
eBay, BMW, Citigroup is Atlassian customers.
Rumors of Fortune 500 companies, the 80% have used JIRA.

The core concept of JIRA

Project (Project)
JIRA The project is a set of issues (Issue), the project can be defined according to organizational needs, such as: software R & D projects, marketing campaigns, help desk (helpdesk) system, a leave management system and so on. Each question belong to a single project. Each project needs to have a name (for example: Website Issues) and keyword (Key, such as the WEB) . The project will be the key item questionnaire prefix, such as WEB-101, WEB-102 and so on.

What is the component (component)

Component is a problem in a single project a logical grouping. A project organization's needs may include a variety of components.
For example, a software development project can include the following components: document, backend, mail subsystem interface. A website system might include product, contact information and other components. In one project, a problem can be attributed to a single zero to the plurality of components.

What version (version)

For some types of projects, especially software development project, to associate a single question to a specific version of the project (for example: 1.0 beta, 1.0, 1.2, 2.0) can be very useful.
Questionnaire (Issues) There are two versions with the related fields:

Affects Version (Affects. Version (S)) - This is to illustrate the impact of single-issue editions For example, a software Bug could affect 1.1 and 1.2 versions.
Fix Version (Fix Version (S)) - this is to indicate the problem is fixed in which a single version. Continuing the example above, Bug affect the version number is 1.1 and 1.2, but was only likely to be fixed in version 2.0. Problem is not fixed version of the single will be classified as unplanned (Unscheduled).

Version can be one of three states the following:

Release (Released)
Unpublished (Unreleased
Archive (Archived)

Version will have a release date, and if it is not released in time after the release date, the state will automatically become expired status (overdue).

Workflow (Workflow)

JIRA Workflow (statuses) and transitions (transitions) consists of a series of states, a single problem in their life cycle will go through these states and transitions. The following figure as an example:

Built-in JIRA Workflow

Issue (questionnaire)

JIRA questionnaire is very flexible and can be customized page, the fields can also be defined. Introduce some basic concepts built here.

Issue Type (questionnaire type)

JIRA can be used to track different types of questionnaires. The default type as follows, JIRA system administrator may also customize these types.

Bug - failure, functional failure
Improvement - to enhance both enhancements
The Feature New - New Features
Task - task
Issue Custom - customized according to customer needs

Priority (priority)

The priority can also customize the default priority is as follows:

Highest - the highest level, indicating a problem blocking the normal business processes
High - senior, show problems caused by evident failure, requiring urgent attention
Medium - Intermediate, indicates that the problem has a significant impact
Low - low, indicates that the problem has a minor impact
Lowest - lowest level

Status (state)

Each issue will have a single current state.
One problem may be single-Open beginning state, may then be transferred to a Resolved or Closed, it depends on how the system flow configuration. Built-in common states are as follows:

Open - open, indicating that the questionnaire has been created, waiting to be assigned to start processing status.
Progress the In - Processing state, it indicates that the problem has already been assigned a single person activated, and in the processed state.
To Resolved - Resolved state, indicating that the problem has been processed, wait for the report to verify people's problems. From this state, the general questionnaire can be further changed to reopen the state (Reopened) or closed (Closed).
Reopened - to re-open, the problem can verify that it is not resolved, you can change to this state.
Closed - the closed state, the problem is completely solved can turn this state.

Resolution (Resolution Outcomes)

A problem can solve a variety of results, only one of which is to fix. One solution is usually the result of changes in the state when they were set up. The default result will be to solve the following problem:

Fixed - fixed.
Not Fix by Will - without repair. For example, it described the phenomenon this problem is no longer the influential.
Duplicate - repeat. Repeat with the other already existing problems, it is recommended to link the relevant list.
Is in Incomplete state - unfinished. There is not enough information to finish the question.
Not Reproduce CAN - can not reproduce. If there is more information in the future may continue to re-open this list.
The Do not by Will - do not do. Do not fix similar programs, the default state to try software projects.