fix direct links to comments

tsa/howto/grafana.mdwn

@@ -13,7 +13,7 @@ Puppet implementation
 Grafana was installed with Puppet using the upstream Debian
 package, following a debate regarding the merits of Debian packages
 versus Docker containers when neither are trusted, see [this
-comment](https://bugs.torproject.org/29684#comment:3) for a summary.
+comment](https://gitlab.torproject.org/legacy/trac/-/issues/29684#note_2316840) for a summary.
 
 Some manual configuration was performed after the install. An admin
 password reset on first install, stored in `tor-passwords.git`, in

tsa/howto/irc.mdwn

@@ -175,7 +175,7 @@ automatically regenerate it every ~90 days :)
 
 They don't need to put the cert/keys anywhere special for you as long as the
 ircbouncer user can access them. See how in
-[this ticket comment](https://bugs.torproject.org/32532#comment:5)
+[this ticket comment](https://gitlab.torproject.org/legacy/trac/-/issues/32532#note_2342136)
 ...
 
     root@chives:~# ls -al /etc/ssl/private/ircbouncer.torproject.org.* /etc/ssl/torproject/certs/ircbouncer.torproject.org.crt*

tsa/howto/puppet.mdwn

@@ -589,7 +589,7 @@ as well.
 Revocation procedures problems were discussed in [33587][] and [33446][].
 
 [33587]: https://bugs.torproject.org/33587
-[33446]: https://bugs.torproject.org/33446#comment:17
+[33446]: https://gitlab.torproject.org/legacy/trac/-/issues/33446#note_2349434
 
  1. Clean the certificate on the master
 

tsa/howto/submission.mdwn

@@ -90,7 +90,7 @@ much problem, their emails often get dropped to the floor when
 It is suspected that users are having those problems because the
 originating servers are not in the `torproject.org` domain. The hope
 is that setting up a new server inside that domain would help with
-delivery. There's anecdotal evidence (see [this comment](https://bugs.torproject.org/30608#comment:8) for
+delivery. There's anecdotal evidence (see [this comment](https://gitlab.torproject.org/legacy/trac/-/issues/30608#note_2325187) for
 example) that delivery emails from existing servers (over SSH to
 `iranicum`, in that example) improves reliability of email delivery
 significantly.

tsa/howto/upgrades.mdwn

@@ -32,7 +32,7 @@ upgrade, however.
 Team policies:
 
  * anti-censorship: TBD
- * metrics: one or two work-day advance notice ([source](https://bugs.torproject.org/32998#comment:2))
+ * metrics: one or two work-day advance notice ([source](https://gitlab.torproject.org/legacy/trac/-/issues/32998#note_2345807))
  * funding: schedule a maintenance window
  * git: TBD
  * gitlab: TBD

tsa/meeting/2019-06-03.mdwn

@@ -51,7 +51,7 @@ halfway through the meeting.
    `loginctl --enable-linger` instead of starting from `cron`
 
    [documented]: https://help.torproject.org/tsa/doc/services/
-   [deployed]: https://bugs.torproject.org/30472#comment:12
+   [deployed]: https://gitlab.torproject.org/legacy/trac/-/issues/30472#note_2323921
 
  * usual tickets triage, support and security upgrades
 

tsa/meeting/2020-02-03.mdwn

@@ -221,7 +221,7 @@ the process will be submitted for discussion this week.
 # TPA-RFC-2: support policies
 
 A *second* RFC would be a formalization of our support policy, as per:
-https://bugs.torproject.org/31243#comment:4
+https://gitlab.torproject.org/legacy/trac/-/issues/31243#note_2330904
 
 Postponed to the RFC process.