Add subscription troubleshooting page

What does this MR do?

Adds a troubleshooting page for GitLab.com and self-managed subscription, because some errors were duplicated on the two pages, and the .com troubleshooting section had five topics so it required a new page.

Related issues

• CTRT - Gitlab.com Subscription (#476443 - closed)
• technical-writing#1078
• technical-writing#1075

Author's checklist

• Optional. Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• If you're adding a new page, add the product availability details under the H1 topic title.
• If you are a GitLab team member, request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

• ~"frontend"
• ~"backend"
• ~"type::bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

• If the content requires it, ensure the information is reviewed by a subject matter expert.
• Technical writer review items:
  • Ensure docs metadata is present and up-to-date.
  • Ensure the appropriate labels are added to this MR.
  • Ensure a release milestone is set.
  • If relevant to this MR, ensure content topic type principles are in use, including:
    • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
    • Any task steps should be written as a numbered list.
    • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
• Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.

added Category:Subscription Management OKR Technical Writing devopsfulfillment docs-only docsimprovement documentation groupsubscription management maintenancerefactor sectionfulfillment twdoing typemaintenance labels

assigned to @lciutacu

	2 Warnings
	fdc798de: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.
	73c89704: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.

	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:

• doc/subscriptions/gitlab_com/gitlab_subscription_troubleshooting.md (Link to current live version)
• doc/subscriptions/gitlab_com/index.md (Link to current live version)
• doc/subscriptions/self_managed/index.md (Link to current live version)

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

changed milestone to %17.4

added 1 commit

• fdc798de - Edit language

Compare with previous version

@jglassman1 Here's the new combined troubleshooting page, like we discussed yesterday. Would you and @fneill please review it?

requested review from @jglassman1 and @fneill

@lciutacu LGTM apart from adding in the GitLab.com only detail to the link subs to namespace section.

resolved all threads

added 1 commit

• 4021ef39 - Specify offering for linking error

Compare with previous version

approved this merge request

added 1 commit

• e57e4b03 - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

reset approvals from @jglassman1 by pushing to the branch

approved this merge request

enabled automatic add to merge train when checks pass

resolved all threads

approved this merge request

added this merge request to the merge train at position 2

removed this merge request from the merge train because the pipeline did not succeed. Learn more.

enabled automatic add to merge train when checks pass

added this merge request to the merge train at position 8

merged

mentioned in commit 06319cec

mentioned in merge request gitlab-docs!5020 (merged)

added OKR workflowstaging-canary labels and removed OKR label

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label

added workflowpost-deploy-db-production label and removed workflowproduction label

added releasedcandidate label

added releasedpublished label and removed releasedcandidate label