Skip to content

Re-add namespaces to sync branches/commits

Anton Smith requested to merge docs/readd-namespaces-sync-branches-commits into master

What does this MR do?

We mention this in our docs:

After you add a group, the following data is synced to Jira for all projects in that group:

- Existing branches and commits (GitLab 15.11 and later)

The current documentation doesn't explain how this works on existing namespaces that were added prior to GitLab 15.11.

So if users upgrade to GitLab 15.11, the documentation as it reads now seems to imply that existing branches and commits will now sync over. However that isn't true, and existing branches and commits are only synced when the namespace is added for the first time.

This MR addresses that point.

Also see https://gitlab.slack.com/archives/C04RDL3MEH5/p1686012368095029

Related issues

Author's checklist

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.

Merge request reports