Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
326c1b5a
G
gitlab-foss
项目概览
李少辉-开发者
/
gitlab-foss
通知
15
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
gitlab-foss
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
前往新版Gitcode,体验更适合开发者的 AI 搜索 >>
提交
326c1b5a
编写于
7月 03, 2017
作者:
M
Marcia Ramos
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
copyedit == ee !2296
上级
ed503c98
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
49 addition
and
23 deletion
+49
-23
doc/user/project/issue_board.md
doc/user/project/issue_board.md
+49
-23
未找到文件。
doc/user/project/issue_board.md
浏览文件 @
326c1b5a
# Issue Board
>**Notes:**
-
[
Introduced
][
ce-5554
]
in GitLab 8.11.
-
The Backlog column was replaced by the
**Add issues**
button in GitLab 8.17.
>**Note:**
[
Introduced
][
ce-5554
]
in
[
GitLab 8.11
](
https://about.gitlab.com/2016/08/22/gitlab-8-11-released/#issue-board
)
.
The GitLab Issue Board is a software project management tool used to plan,
organize, and visualize a workflow for a feature or product release.
...
...
@@ -15,36 +14,63 @@ Other interesting links:
## Overview
The Issue Board builds on GitLab's existing issue tracking functionality and
The Issue Board builds on GitLab's existing
[
issue tracking functionality
](
issues/index.md#issue-tracker
)
and
leverages the power of [labels] by utilizing them as lists of the scrum board.
With the Issue Board you can have a different view of your issues while
also
With the Issue Board you can have a different view of your issues while
maintaining the same filtering and sorting abilities you see across the
issue tracker.
issue tracker. An Issue Board is based on its project's label structure, therefore, it
applies the same descriptive labels to indicate placement on the board, keeping
consistency throughout the entire development lifecycle.
## Use cases
An Issue Board shows you what issues your team is working on, who is assigned to each,
and where in the workflow those issues are.
You create issues, host code, perform reviews, build, test,
and deploy from one single platform. Issue Boards help you to visualize
and manage the entire process _in_ GitLab.
There are numerous use cases for Issue Boards, we will just
exemplify with a couple situations.
With
[
Multiple Issue Boards
](
https://docs.gitlab.com/ee/user/project/issue_board.html#multiple-issue-boards
)
, available
only in
[
GitLab Enterprise Edition
](
https://about.gitlab.com/gitlab-ee/
)
,
you go even further, as you can not only keep yourself and your project
organized from a broader perspective with one Issue Board per project,
but also allow your team members to organize their own workflow by creating
multiple Issue Boards within the same project.
## Use cases
GitLab Workflow allows you to discuss proposals in issues, categorize them
with labels, and from there organize and prioritize them with Issue Boards.
-
For example, let's consider this simplified development workflow:
you have a repository hosting your app's codebase
and your team actively contributing to code. Your backend team starts working a new
implementation, gathers feedback and approval, and pass it to frontend.
From there, when frontend is complete, the new feature
is deployed to staging to be tested. When successful, it goes to production. If we have
the labels "backend", "frontend", "staging", and "production", and an Issue Board with
a list for each, we can:
-
Visualize the entire flow of implementations since the
beginning of the dev lifecycle until deployed to production
-
Prioritize the issues in a list by moving them vertically
-
Move issues between lists to organize them according to the labels you've set
For a broader use-case, please check the blog post
For example, let's consider this simplified development workflow:
1.
You have a repository hosting your app's codebase
and your team actively contributing to code
1.
Your
**backend**
team starts working a new
implementation, gathers feedback and approval, and pass it over to
**frontend**
1.
When frontend is complete, the new feature is deployed to
**staging**
to be tested
1.
When successful, it is deployed to
**production**
If we have the labels "
**backend**
", "
**frontend**
", "
**staging**
", and
"
**production**
", and an Issue Board with a list for each, we can:
-
Visualize the entire flow of implementations since the
beginning of the development lifecycle until deployed to production
-
Prioritize the issues in a list by moving them vertically
-
Move issues between lists to organize them according to the labels you've set
-
Add multiple issues to lists in the board by selecting one or more existing issues
![
issue card moving
](
img/issue_board_move_issue_card_list.png
)
> **Notes:**
>
>- For a broader use case, please check the blog post
[
GitLab Workflow, an Overview
](
https://about.gitlab.com/2016/10/25/gitlab-workflow-an-overview/#gitlab-workflow-use-case-scenario
)
.
>
>- For a real use case, please check why
[
Codepen decided to adopt Issue Boards
](
https://about.gitlab.com/2017/01/27/codepen-welcome-to-gitlab/#project-management-everything-in-one-place
)
to improve their workflow with
[
multiple boards
](
https://docs.gitlab.com/ee/user/project/issue_board.html#multiple-issue-boards
)
.
## Issue Board terminology
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录