debian-mirror-gitlab/data/whats_new/202008180003_13_01.yml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

50 lines
3.1 KiB
YAML
Raw Normal View History

2020-10-24 23:57:45 +05:30
---
- title: Manage IT Alerts in GitLab
2021-02-22 17:27:13 +05:30
body: |
GitLab is excited to introduce Alert Management to aggregate multiple IT service alerts in one interface, helping your team triage alerts and promote them to Incidents.
Weve added the ability to triage alerts in a [list view](https://gitlab.com/groups/gitlab-org/-/epics/2986), [view alert details](https://gitlab.com/groups/gitlab-org/-/epics/2987), [assign alerts](https://gitlab.com/groups/gitlab-org/-/epics/3349), [update the status of alerts](https://gitlab.com/gitlab-org/gitlab/-/issues/214542), and [create Incident Issues from Alerts](https://gitlab.com/gitlab-org/gitlab/-/issues/213909).
2020-10-24 23:57:45 +05:30
stage: Monitor
self-managed: true
gitlab-com: true
2021-03-11 19:13:27 +05:30
packages: [Free, Premium, Ultimate]
url: https://docs.gitlab.com/ee/operations/incident_management/index.html
2020-10-24 23:57:45 +05:30
image_url: https://about.gitlab.com/images/13_1/alert_management.png
published_at: 2020-06-22
release: 13.1
2021-04-29 21:17:54 +05:30
- title: Accessibility testing merge request widget
2021-02-22 17:27:13 +05:30
body: |
Today, developers who want to ensure their application is accessible to everyone suffer from slow feedback loops, which make it difficult to catch degradations in their code.
In GitLab 13.1, merge requests can have a widget that details accessibility degradations related to the changed pages. This will immediately show developers the impact of their changes, which helps prevent degradations before they are merged and deployed.
2020-10-24 23:57:45 +05:30
stage: Verify
self-managed: true
gitlab-com: true
2021-03-11 19:13:27 +05:30
packages: [Free, Premium, Ultimate]
2020-10-24 23:57:45 +05:30
url: https://docs.gitlab.com/ee/user/project/merge_requests/accessibility_testing.html#accessibility-merge-request-widget
image_url: https://about.gitlab.com/images/13_1/a11y-merge-request-widget.png
published_at: 2020-06-22
release: 13.1
- title: Mark any Design Thread as Resolved
2021-02-22 17:27:13 +05:30
body: |
When you receive lots of feedback on a Design, the number of comment pins can build up quickly! As your discussion thread grows, it gets hard to know which discussions are complete and which still need work. Now youll have the ability to mark any comment as **Resolved** to signify that it is now complete. Even better — your **Resolved Comment** pins will disappear from the Design so you can focus on whats left!
2020-10-24 23:57:45 +05:30
stage: Create
self-managed: true
gitlab-com: true
2021-03-11 19:13:27 +05:30
packages: [Free, Premium, Ultimate]
2020-10-24 23:57:45 +05:30
url: https://docs.gitlab.com/ee/user/project/issues/design_management.html#resolve-design-threads
image_url: https://about.gitlab.com/images/13_1/resolve-design-comment.gif
published_at: 2020-06-22
release: 13.1
2021-04-29 21:17:54 +05:30
- title: Merge request reviews moved to Free
2021-02-22 17:27:13 +05:30
body: |
2021-04-29 21:17:54 +05:30
Originally introduced in GitLab 11.4 as a GitLab Premium feature, merge request reviews allow merge request reviewers to submit multiple comments at once, cutting down on notification noise for the merge request author, and allowing for a more cohesive and streamlined review process.
2020-10-24 23:57:45 +05:30
stage: Create
self-managed: true
gitlab-com: true
2021-03-11 19:13:27 +05:30
packages: [Free, Premium, Ultimate]
2020-10-24 23:57:45 +05:30
url: https://docs.gitlab.com/ee/user/discussions/index.html#merge-request-reviews
image_url: https://about.gitlab.com/images/13_1/batch_comments.png
published_at: 2020-06-22
release: 13.1