Original address:About.gitlab.com/2018/08/02/…
The writer isGitLabThe team’s product managerVictor Wu“Written on August 2, 2018
With labels, GitLab Issues can be easily customized to support various workflows. This article lists four examples.
There are many ways to build software and run projects. When we started building the portfolio and project management tools within GitLab, we asked ourselves, “How do you build tools that support different workflow queues without sacrificing complexity to users?” Our conclusion? Is to build fewer and more flexible tools. Gitlab’s built-in Issue panel is a perfect example of how choosing to build a single, universal tool can significantly reduce complexity and user maintenance tools without limiting their capabilities.
Managing projects and software is inherently complex, but tools don’t have to be. No matter how many projects, how many people, or how many products you manage, it should be clear what makes things run smoothly.
GitLab’s Issue panel is a shortcut to dealing with complex issues. We built the Issue panel on top of Gitlab’s existing issue-Tracking feature by taking tags and arranging them in a Kanban board. You can construct different views and keep the same filters and sorting functionality that you see in the Issue Tracker. You can also create multiple panels to visually capture each layer required and define the scope of the panel through milestones, labels, assigns, weights, and so on.
The Issue panel is based on the tag structure of its project, so it follows the same descriptive tags to guide the panel configuration and ensure consistency throughout the development cycle. Alternatively, you can just click on an issue on the panel to start your work.
An Issue panel shows you the issues your team is facing, who has been assigned what, and how far those issues have progressed.
1. Workflow tracking
Whether you’re a project manager who wants to see the big picture, or a product manager who needs to report progress, visual workflows are important.
To create a workflow Issue panel, simply create a label for each stage of your workflow and arrange them in the panel. When the problem is resolved and ready to move on to the next stage, just drag and drop it to the next list. You can also update the label directly in the Issue, and the changes will automatically appear in the panel.
For example, suppose your workflow looks something like this:
- The development of
- design
- review
- test
- The deployment of
Just create a label for each stage to see these in the palette. Create a new panel and Add a List for each stage, or drag and drop the List to order it appropriately.
2. Create cross-functional plans based on categories
Similar to the workflow view, an Issue panel can also be created based on categories.
When working on a particular product or feature, you might want to take a high-level look at how each team is doing. You can certainly create a label and a list for each team, or, if you want to see horizontally what multiple projects or product lines are doing.
In the example above, we have three tag lists: time tracking, portfolio management, and description templates. Each list represents a specific product area. In this panel, you can see the open Issues and their respective areas. If you want to treat this panel as a specific milestone in the future, you’ll be able to see which issues point to the work in progress at that time.
This is just one example of how to use the Issue panel. Again, since the Issue panel is created based on tags, your options are infinite!
3. Team visualization with a list of appointees
The list of appointees makes it easy to see what tasks each person on the team has been assigned. The list of assigns shows issues assigned to a particular user, and you can also create a panel to display a list of each member of a team to quickly understand who is doing what.
(This feature is supported natively from version 11.0)
4. Milestones coming soon
As part of our project management capabilities, we built in milestones. Milestones are used to track issues and merge requests related to a specific goal achieved at a specific time.
In the next release (11.2 on August 22), we added milestones to the list. Similar to the list of appointees, you can quickly create a milestone view directly from the palette. This is especially useful for agile development. Milestone lists make it easy to move issues between milestones such as sprints, iterations.
| Adding a Milestone List | Milestone list |
|---|---|
 |
 |
Of course, this is just the tip of the iceberg. Stay tuned for future posts on using GitHub for organizational planning and management, which will cover other interesting features such as Epics, roadmaps, and milestones.
–End–
Search fewelife concern public number reprint please indicate the source