Author: Ruan Yi Feng
Date: August 29, 2017
Software development (especially commercial software) is inseparable from project management, and Issue is one of the most common management tools.
This article introduces the basic usage of Issue.
One, Issue is what.
Issue refers to a work to be done, usually related to system improvement, in which Chinese can be translated as "problem" or "transaction". Here are some examples of Issue. A software bug a feature suggests a report that is missing from a pending task document
Each Issue should contain all the information and history of the problem, making it possible for later people to look at the Issue and understand all aspects and processes of the problem.
Historically, Issue originated in the customer service department. User calls to reflect the problem, customer service to create a work order (ticket), followed by each of the processing steps, every time with the user's communication, to update the work order, record all information. This is the predecessor of Issue.
As a result, the original function of Issue is problem tracking and work order management, and then expanding, gradually evolving the function of the project management tools, can also be used to develop and implement software development plans.
In addition to software, other projects can also use Issue, such as someone to make their own home improvement plans have been made Issue. Second, Issue tracking management system
The software that specializes in managing Issue is called the Issue Tracking Management system (Issue tracking systems). It is intended for everyone and can be used by ordinary users.
There is also a Bug tracking management system that is typically targeted only at developers, such as the Bugzilla of the image below. It can be used at the same time as the Issue system, but can also be replaced by the Issue system.
Generally speaking, the Issue tracking management system should have the following functions. Project Management
-Specifies the priority of the Issue
-Specifies the stage where Issue is located
-Assign responsible Issue to the processing staff
-Make a schedule
-Monitor progress and provide statistical team work
-Mail Notification code management
-Issue associated with the source code
-Submit Issue associated code to merge three, Github Issues
At present, the most famous Issue tracking management system is JIRA. It is a billing software, which is not introduced here. The following is a free Github Issues to describe how to use Issue.
3.1 Basic usage
Each Github code warehouse has a Issues panel.
Enter the panel, click on the "New Issue" button, you can create a new Issue.
The image above is the new Issue interface, with the Issue title and content on the left, and four configuration items on the right (only the project manager can see it). Assignees: Personnel Labels: Tags Projects: project Milestone: Milestones
Below, describe each of these configuration items. 3.2 Assignee
The Assignee selection box is used to assign a Issue handler from among all members of the current warehouse.
Click the name in the Drop-down box. 3.3 Labels
Issue can be labeled, which facilitates sorting management and filtering views.
To create a new label, click the Labels button on the front page of the Issues panel.
At this point, six default labels are displayed.
If you want to create more labels, you can click the New Label button. Then, fill in the label name and select the label color.
3.4 Common Label
For large projects, there should be at least two labels per Issue, one representation, and the other a priority.
A Label that represents a property, you can refer to the example of this article.
Represents the priority Label, which can take the following level. High priority: Has a significant impact on the system, and only after it is resolved can other tasks be completed. Normal priority (Medium): A part of the system has an impact, the user's part of the operation will not achieve the desired effect. Lower priority (Low): an impact on a part of the system that is almost imperceptible to the user. Trivial (Trivial): No effect on the function of the system, usually the visual effect is not ideal, such as font and color is not satisfied. 3.5 Milestone
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.
3.6 Global View
The Issues panel can only view and manipulate the current warehouse, Github also provides a global view that allows users to view and manipulate all the Issue associated with them.
Access to github.com/issues this URL, you can open the global view. The Issue are divided into three categories.
Created: The Issue assigned that you create: Issue mentioned that you have assigned to you: mention your Issue
The meaning of Created and assigned is obvious, mentioned refers to others in Issue @ you. Here is an example.
It looks like the new widget form was broken on Safari. When I try and create the widget, Safari crashes. This is reproducible on 10.8 and but not 10.9. Maybe a browser bug?
/CC @kneath @jresig
The global view also provides search, filtering, and sorting capabilities.
Four, Kanban function 4.1 kanban is what.
Kanban (Kanban) is an important means of agile development, which is mainly used in project schedule management. All the tasks that need to be done are made into cards and posted on a whiteboard, which is the kanban.
At different stages, the Kanban is divided into several columns. The above diagram is a common method of dividing the project cycle into three columns. Todo (to be developed) doing (in development) done (completed)
You can classify more columns according to the actual situation.
Todo (to be scheduled) plan develop (development) test (test) Deploy (deployed) done (completed) 4.2 Github Kanban function
Github provides Issue kanban. First, enter the Projects panel on the front page of the warehouse.
Then, click the New Project button to create a new project, such as "version 2.0."
Next, click the Add column button to create a few new columns for the item.
Finally, the Issue is assigned to the corresponding column, and a new Kanban view is successfully created.
Issue can be dragged from one column to another to indicate a phase from one stage to another.
Many Third-party tools can enhance the Github kanban function, the most famous is Zenhub, here is not described in detail.
Five, Issue system of code cloud
In addition to Github, Gitlab also offers free Issues management systems and is easier to use than the former. But I'm not going to introduce it, I want to introduce the code-managed Service Code Cloud (gitee.com) launched by the Open source China community.
The code cloud is the depth customization of the Gitlab, provides the Chinese interface, conforms to the people's usage habit, and the access speed is extremely fast, I feel is quicker than gitlab a order of magnitude. On the other hand, open source China's sweet potato boss has been supporting me, I would like to take this opportunity to promote their products, so that more people know this excellent domestic SaaS service. 5.1 New Issue
Every warehouse in the code cloud has a Issues panel. After entering, click New Issue, you can create a Issue, inside the set item than Github rich many. (Note that only the administrator of the warehouse can see the settings item.) ）
The "owner" (Assignee), label, Milestone (Milestone) is exactly the same as Github. The Associate branch specifies which branch the Issue belongs to, and the start time and end time specify the processing schedule. The "top option" specifies which Issue appear at the front, and is also divided into high school and three stalls.
The Issue list offers more filter switches because of more settings.
5.2 Kanban function
The code Cloud's Kanban function is more user-friendly than the Github, providing four off-the-shelf kanban directly.
Pending process completed already accepted
The initial state of all Issue is pending, and users can manually drag them to other columns. 5.3 Enterprise Edition
The code cloud, like Gitlab, also offers an enterprise version. The "task" module inside has a powerful Issue global view, divided into four browsing modes.
Assigned to me, I released all the tasks I participated in
This is the default list view, and you can click on the top right corner to switch to the global Kanban view.
This interface can also create a new task directly without having to go to the Warehouse home page. When you create a new task, you allow you to specify associated items, owner, and expected work.
After you create a new task, you can edit the task again, setting priority, associated items, and subprojects.
I introduced here, next you can click into the Demo, experience the above features described above.