Using issue to manage software projects (Getting started)

As long as the software development, several people to cooperate, you must carry out project management, issue is one of the most common management tools. One, what is issue

Issue refers to a work to be done, usually related to the improvement of the system. Chinese is called "problem", but I prefer another term "business". A software bug a feature suggests a pending task document description missing report

All of these are examples of issue. Each issue contains all the information and history of the transaction, making it possible for later people to look at the issue and understand all aspects and processes of the problem.

This original prototype is the customer service department's work list, each processing step, and communicates with the user must update the work order, records all information. Therefore, the original function of issue is problem tracking and work order management, and then constantly expand, including planning, milestone establishment, and gradually improve the project management process. Second, issue software

In fact, there are many issue software, but here I do not want to introduce, used Bugzilla,jira,mantis,bugfree (Zen Road) There are many assorted software, but strong to strong, excellent return to excellence. There are common drawbacks to these software. Complex function, high learning cost interface compared to human beings, must be in-depth understanding of the need to use the offline deployment, installation complex (authorization, high fees, small companies will not use)

A lot of people who want to learn the relevant knowledge will soon be interested. Or the introduction has given free simple, and programmers should learn the most GitHub Issues. 2.1 Basic Usage

Click on the issues panel in the GitHub Code warehouse, Newissue button to add a new issue panel

The image above is the newly created issue interface with the title and content of issue on the left and four configuration items on the right (visible to the manager)

Assignee, select people, assign issue handlers

Labels, for issue labeling, facilitate the classification of management and filter view (new tag in the Issues Panel homepage, click Labels, but please use the default first)

Projects, project (actually used Kanban, you can think that project is a fast collation issue state of Kanban, Todo,in Progress, done three states)

According to my habit there should be another plan, if there is a full-time tester, there is a testcomplete.

Milestone: Milestones, 2.2Label of Use

Each issue has at least two lable, one representing the nature, one representing the priority (in a more complete bug and project management system, which would have been separate)

The nature of the article can be joined. Priority can be set as follows: High priority: A significant impact on the system, only to resolve it to complete other tasks. Common priority (Medium): A part of the system has an impact, the user part of the operation can not achieve the desired effect. Lower priority (Low): a part of the system is affected, but the user is almost imperceptible. It is best to have (Nicetohave): No effect on the function of the system, usually the visual effect is not ideal (font, color) or some personal preference problems. 2.3MileStone

Milestone is called "milestones" and is used as a Issue container, and the associated Issue can be placed in a Milestone. The common examples are different versions (version) and iterations (sprints), which can be made into Milestone.

New Milestone, to the front page of the Issues panel, click on the Milestones button.

Then click the New Milestone button and fill in the name and content of milestone, and specify the expiration time.

If you are in issue, you will see this issue in the mentioned in the global view issues. Third, Kanban function

Kanban (Kanban) is an important means of agile development, mainly used for project progress management, all the tasks need to be done, are made into cards, affixed to a whiteboard above, this is Kanban.

At different stages, the Kanban is divided into several columns. The most basic is Todo (to be developed) doing (in development) done (completed)

Of course you can make more columns according to the actual situation. For example, plan plans, deploy deployments, test tests, can all be added. The goal is that all affairs (Issue) are moved to the done. Open the projects interface in GitHub to see the corresponding interface, where I have created 3 classic Colum. You can add more processes to your own management needs.

Don't hesitate to start your GitHub trip right away. If you feel that your English is not good, or worry about network problems, you can also use the Open source China Community Code managed Service Codes Cloud (gitee.com).