GitLab.md

 This is about migrating our data and workflow from Redmine to GitLab,
-which is tracked as [[!tails_ticket 15878]].
+which is tracked as tails/tails#15878.
+
+
+[[_TOC_]]
 
-[[!toc levels=3]]
 
 <a id="access-control"></a>
 
@@ -103,7 +105,7 @@ which is tracked as [[!tails_ticket 15878]].
  - Release managers have "Reporter" access to every project in this group
    (after releasing a new Tails, they need to postpone issues,
    including confidential ones, and manage group labels),
-   until [[!tails_ticket 17589]] is done.
+   until tails/tails#17589 is done.
  - Nobody else is a member of this group.
  - Allow users to request access: disabled
 
@@ -251,7 +253,7 @@ subgroups merely to simplify access level management.
 It's out of scope for the first iteration but at some point, we might
 want to migrate our blueprints to GitLab's
 [wiki](https://docs.gitlab.com/ce/user/project/wiki/):
-[[!tails_ticket 9174]]).
+tails/tails#9174).
 
 <a id="git"></a>
 
@@ -345,7 +347,7 @@ Pushing to our Git repository pings Jenkins so it can run jobs as needed:
 Jenkins jobs are generated on `jenkins.lizard`, from the list of
 branches in our main Git repository. For details and pointers to the
 corresponding code, see the corresponding
-[[blueprint|blueprint/automated_builds_and_tests/jenkins]].
+[blueprint](automated_builds_and_tests/jenkins).
 
 Here are the kinds of jobs relevant in this discussion:
 
@@ -412,7 +414,7 @@ to issues and merge requests:
   - <https://gitlab.com/gitlab-org/quality/triage-ops>
   - <https://gitlab.com/gitlab-org/gitlab-triage>
 
-Potential future work: [[!tails_ticket 17589]].
+Potential future work: tails/tails#17589.
 
 ## Translation platform → Git
 
@@ -455,3 +457,4 @@ See <https://salsa.debian.org/tails-team/gitlab-migration/wikis/hosting/comparis
   but attributed in the comment itself to their original author.
   Commits are authored by the original author.
   Example: <https://0xacab.org/tails/test-import/>
+