Skip to content
Snippets Groups Projects

Release post - GitLab 11.4

Merged James Ramsay (ex-GitLab) requested to merge release-11-4 into master
Compare and Show latest version
3 files
+ 49
0
Compare changes
  • Side-by-side
  • Inline
Files
3
@@ -159,6 +159,55 @@ features:
# SECONDARY FEATURES
secondary:
- name: "Include new issues created in burndown chart"
available_in: [starter, premium, ultimate]
documentation_link: 'https://docs.gitlab.com/ee/user/project/milestones/burndown_charts.html'
image_url: '/images/11_4/burndown-chart.png'
reporter: victorwu
team: plan
issue_url: 'https://gitlab.com/gitlab-org/gitlab-ee/issues/6174'
description: |
Burndown charts help teams track work, as it progresses throughout a milestone.
Usually, the scope of work is decided and agreed on before the milestone
begins. But occasionally, there will be important exceptions to the rule,
(such as an emergency bug or security fix) and new scope needs to be included,
in the form of new issues.
With this release, the burndown chart now accounts for these
new issues that are created in the middle of a milestone, resulting in an
uptick of the line in a burndown chart.
- name: "Expanded weight values in issues API"
available_in: [starter, premium, ultimate]
documentation_link: 'https://docs.gitlab.com/ee/api/issues.html'
reporter: victorwu
team: plan
issue_url: 'https://gitlab.com/gitlab-org/gitlab-ee/issues/6822'
description: |
In a previous release, we expanded the allowable values of issue weight
from a small number to effectively unlimited, any number greater than zero.
With this release, we've brought this flexibility to the issues API as well,
allowing users to set this field with the new expanded number range with
the API.
- name: "Lock discussion quick action"
available_in: [core, starter, premium, ultimate]
documentation_link: 'https://docs.gitlab.com/ee/user/project/quick_actions.html'
image_url: '/images/11_4/lock-discussion-quick-action.png'
reporter: victorwu
team: plan
issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/39173'
description: |
Locking discussions in issues and merge requests is helpful to direct conversations
to newer issues (or merge requests). It can also be used to control abusive
or otherwise unproductive behavior.
With this release, we now have quick actions to lock and unlock discussions,
making it easier to type a comment and lock/unlock all one action.
Thank you [Mehdi Lahmam](https://gitlab.com/mehlah) for the contribution!
- name: "Close epics"
available_in: [ultimate]
documentation_link: 'https://docs.gitlab.com/ee/user/group/epics/'
Loading