英文:

Epics/stories in GitLab FOSS

问题

我们有一个自托管的GitLab FOSS实例。这个版本不包含任何史诗/故事，并且没有内置的方法来创建问题之间的层次结构。

我们正在从JIRA迁移一个项目。曾经在这个项目上工作的团队使用了史诗/故事和子任务。在GitLab FOSS中处理史诗/故事是否有任何策略？我的意思是，我知道我们可能需要使用标签和/或里程碑，但是否有人遇到过这种情况？

此外，我知道GitLab Ultimate有史诗功能，但价格太昂贵了。

英文:

We have a self-hosted GitLab FOSS instance. This version does not include any epics/stories and there is build-in way to create hierarchy between issues.

We are migrating a project from JIRA. The team that worked on this project where using epics/stories and sub-tasks. Are there any strategies to handle epics/stories in GitLab FOSS. I mean I know we would have to use labels and/or milestores, but has anyone ran into this situation.

Also, I know GitLab Ultimate has epics, but it is too expensive.

答案1

得分: 1

以下是您要翻译的内容：

Epic in GitLab are indeed part of the "Portfolio Management" feature (issue 3254) of the GitLab Ultimate edition.

唤起GitLab确实是GitLab终极版的“投资组合管理”功能的一部分（问题3254）。

唤起

The only free alternative would be to have "sub-issues," which are being discussed in issue 4588, and illustrate how you would need to use labels.

唯一的免费替代方法将是使用“子问题”，这在问题4588中正在讨论，并说明您需要如何使用标签。

For instance:

例如：

All sub-issues must use the same prefix for their title, preferably a meaningful shortened version of the main issue's title if it's too long.
This is a visual helper to quickly identify sub-issues and their main issue.

所有子问题必须使用相同的标题前缀，最好是主要问题标题的有意义的缩写版本（如果标题太长）。这是一个可视化助手，可以快速识别子问题及其主要问题。

Each sub-issue must have proper labels:

每个子问题必须有适当的标签：

• the ~sub-issue label

• the same type label as the main issue

• the same release scoping label as the main issue

• the same priority label and severity label as the main issue

• the relevant specialization label to that particular sub-issue

• ~子问题标签

• 与主要问题相同的类型标签

• 与主要问题相同的发布范围标签

• 与主要问题相同的优先级标签和严重性标签

• 适用于特定子问题的相关专业标签

This is still being implemented, with topics like "Provide first class support for Issue Task Lists and Tasks" (issue 2036).

这仍在实施中，涵盖了诸如“为问题任务列表和任务提供一流支持”（问题2036）等主题。

Update March 2022 for GitLab 14.9 (Ultimate edition only)

2022年3月的GitLab 14.9更新（仅适用于终极版）

Link an epic to another epic

将史诗与另一个史诗关联起来

GitLab now supports linking epics using “related,” “blocking,” or “blocked” relationships.

现在，GitLab支持使用“相关”，“阻止”或“被阻止”关系来关联史诗。

This feature enables teams to better track and manage epic dependencies across GitLab groups.

此功能使团队能够更好地跟踪和管理GitLab组之间的史诗依赖关系。

Effective dependency management is a key component of reducing variability and increasing predictability in value delivery.

有效的依赖管理是降低变异性并增加价值交付可预测性的关键组成部分。

英文:

Epic in GitLab are indeed part of the "Portfolio Management" feature (issue 3254) of the GitLab Ultimate edition.

The only free alternative would be to have "sub-issues", which are being discussed in issue 4588, and illustrate how you would need to use labels.

For instance:

> All sub-issues must use the same prefix for their title, preferably a meaningful shortened version of the main issue's title if it's too long.
This is a visual helper to quickly identify sub-issues and their main issue.
>
> Each sub-issue must have proper labels:

• the ~sub-issue label
• the same type label as the main issue
• the same release scoping label as the main issue
• the same priority label and severity label as the main issue
• the relevant specialization label to that particular sub-issue

This is still being implemented, with topics like "Provide first class support for Issue Task Lists and Tasks" (issue 2036).

---

Update March 2022 for GitLab 14.9 (Ultimate edition only)

> ## Link an epic to another epic
>
> GitLab now supports linking epics using “related”, “blocking,” or “blocked” relationships.
>
> This feature enables teams to better track and manage epic dependencies across GitLab groups.
>
> Effective dependency management is a key component of reducing variability and increasing predictability in value delivery.
>
>