diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-02-18 12:45:46 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-02-18 12:45:46 +0300 |
| commit | a7b3560714b4d9cc4ab32dffcd1f74a284b93580 (patch) | |
| tree | 7452bd5c3545c2fa67a28aa013835fb4fa071baf /doc/development/issue_types.md | |
| parent | ee9173579ae56a3dbfe5afe9f9410c65bb327ca7 (diff) | |
Add latest changes from gitlab-org/gitlab@14-8-stable-eev14.8.0-rc42
Diffstat (limited to 'doc/development/issue_types.md')
| -rw-r--r-- | doc/development/issue_types.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/issue_types.md b/doc/development/issue_types.md index 31fa50e1d97..e6047c62827 100644 --- a/doc/development/issue_types.md +++ b/doc/development/issue_types.md @@ -11,7 +11,7 @@ We are deprecating Issue Types as of GitLab 14.2 in favor of [Work Items and Wor Sometimes when a new resource type is added it's not clear if it should be only an "extension" of Issue (Issue Type) or if it should be a new first-class resource type -(similar to Issue, Epic, Merge Request, Snippet). +(similar to issue, epic, merge request, snippet). The idea of Issue Types was first proposed in [this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/8767) and its usage was |