Shulou(Shulou.com)06/03 Report--

Recently, there is something wrong with the local bug management software that I am using. I can't remember how many times this is. Every time a problem occurs, I have to spend a lot of time and energy looking for a solution online. In order to avoid this situation again, I decided to move from offline to online and use a lightweight online bug management tool with the following requirements when choosing a tool:

1. You don't need to install and deploy locally, configure the environment and use it immediately.

2. Convenient for bug management and bug attribute setting

3. Ability to communicate across teams and facilitate collaboration with developers

4. Keep abreast of bug status, repair progress, etc.

I spent a week trying out five online bug management tools, and the results are as follows:

1. Teambition

The design of Teambition is simple, elegant, refreshing and straightforward. Registration and login will show all the projects you have participated in (and all projects that have been archived). By default, there is a novice guide project that allows you to get started quickly. After creating a bug project, you can manage bug through functional modules such as "taskpad", "sharing wall" and "document library". And the priority can be set for bug: normal, urgent, very urgent, which is very good, the addition of the tag function can enrich the property settings of bug. On the other hand, the associated task feature can remind the relevant bug to facilitate reference when developing fixes.

However, although teambition's Kanban function can track the status and progress of bug, it can not simply and directly achieve bug version management, to achieve bug version management needs to establish another project to achieve, so the operation will become very tedious, management is also very troublesome, especially in the version comparison is simply painful.

In addition, the bug task cannot be assigned to the developer across the team, so the task can only be copied to the development team's project in the form of a copy task, so that even if the developer fixes the bug and marks the status of the bug as completed, the test cannot be seen in the bug management project, because the task status in different projects cannot be synchronized.

2. Worktile

Worktile and Teambition are highly similar, both have similar Kanban designs, both are task-centric, document files can be archived as task-related content, and both have subtask functions a long time ago, but there is a slight gap in some detailed designs. Worktile can manage bug tasks from different dimensions, such as list, label, time, member, and so on. Through the calendar view, you can easily view the progress of bug tasks; team members can also easily share files and have online discussions in worktile. Worktile's briefing function is a summary of project completion status over a certain period of time, such as how many bug tasks have been started this week, how many bug tasks have been completed, who has completed the most bug tasks, and so on.

Feel stifled!

3. Tower

Tower in the use of habits closer to ordinary users, the interface design is not so "cool", but it can also be clear at a glance. The main functions are discussion, task, document and file. Compared with the function of "discussion", it sets up a forum directly in the collaboration platform, where each member can post and reply to the discussion. posts support rich text format. After creating a project in tower.im, you can assign and manage tasks, discuss project details online, share data files, and collaborate to edit documents online. Through the dynamic message bar, you can view the work of other team members in real time. For team leader, the team weekly report can be used to keep track of the progress of team members.

Tower should be the weakest in bug management, unable to set priorities for bug tasks, enrich bug attributes by tagging, version management, and cross-team communication. After using it for a period of time, I feel that Tower is more suitable as a tool for team brainstorming and personal transaction management.

4. Ming Dao

After the use of the previous software, Mingdao is much faster to get started, because the interface and functions are basically the same, but Mingdao is different from the above three software in that it can switch between list and Kanban mode, which is obviously more friendly when bug is updated, while Kanban is better than list for status tracking. And when editing bug task details, the details page is slide-out, can coexist with the task interface, and the experience is better than the pop-up of teambition and worktile.

With a clear interface and using dynamic information boxes, you can share your work progress, information and feedback questions with the team at any time. In the task center, you can manage tasks in both "task" and "project" modes. When you create a task, you can add a task description, identify the person in charge, participants, and deadlines to move the task forward quickly. Documents, pictures, votes, questions and videos generated in use are automatically archived in the document center for easy retrieval and use at any time. As mentioned above, the function points are mostly similar.

After using it for a period of time, I found that Mingdao is much more convenient than the above software, but it still can not solve my problem: the lack of version management function of bug.

5. Teamin

Teamin is a new software recently, which was recommended by my friends and started to try, which brought me a lot of surprises. First of all, the interface style is so simple that entering the home page is like a notepad, and the way it creates tasks is very much like taking notes: finish a task, enter, and start recording the next. And support the switch between list mode and Kanban mode. After recording the updated bug task in list mode, you can switch to Kanban mode to check the progress of the task. The most important thing is the target management function of Teamin. When I transferred the target management function, I was shocked. Isn't this the version management function I've always dreamed of? And you can assign bug tasks to developers across projects and teams, which is simply not even better. In addition, like other software, there are detailed descriptions of tasks, label functions, and so on, and label fields and colors are supported.

The only regret is that there is no default task priority setting, but this can be solved by likes following tasks or by adding tags and custom fields.

Through the above evaluation, we can see that each of the five software has its own advantages and disadvantages. Personally, Teamin is an online bug management software that can best meet my needs. It is very convenient to help me solve a series of problems such as bug version management, cross-team communication, synchronous tracking of bug progress and so on. However, everyone's needs are different, and the tools or functions they need are also different. As for how to choose and which one to choose as their own bug management tool, there are different opinions. In any case, I hope you can find a suitable bug management tool that can improve your work efficiency.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.