Remove admin mode entry from What's New

What does this MR do?

Removes the Admin Mode entry from What's New since it didn't make the release (see https://gitlab.slack.com/archives/C3TRESYPJ/p1616431821172200 for more details)

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• 📋 Does this MR need a changelog?
  • I have included a changelog entry.
  • I have not included a changelog entry because _____.
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

changed milestone to %13.10

added Pick into 13.10 documentation labels

	1 Message
📖	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

• data/whats_new/202103220001_13_10.yml

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

If needed, you can retry the danger-review job that generated this comment.

Generated by 🚫 Danger

marked this merge request as draft

marked this merge request as ready

@jayswain Mind taking a look at this one too? We had a last-minute change.

@mkarampalas the change looks straight forward enough and the tests have passed (thanks @jayswain). While minor and only a removal, we do need a technical writer to review.

@aqualls could you have a look please? Context here (GitLab internal)

requested review from @aqualls

changed milestone to %13.11

added missed:13.10 label

added devopsgrowth release post release post item tw-weight3 twfinished labels

added groupadoption [DEPRECATED] label

approved this merge request

I'm approving, but I'm routing this over to @axil to make sure it's targeting the right branch. He's handling lead TW duties for %13.10.

assigned to @axil

requested review from @axil

unassigned @jayswain

removed review request for @aqualls

resolved all threads

approved this merge request