Support ticket:1:comment:1 links?

[anonymous]

Trac supports linking to ticket comments: comment:3:ticket:12597

(Here on trac.edgewall.org comment:1:ticket:1 doesn't work?)

(Actually WikiFormatting only mentions: ticket:1#comment:1?)

A similar case is attachments: attachment:ticket:216:report.patch​

But the orderings seem inconsistent:

• realm:parent-realm:parent-id:id (attachment:ticket:216:report.patch​)
• realm:id:parent-realm:parent-id (comment:3:ticket:12597)
• parent-realm:parent-id#realm:id (ticket:1#comment:1)

For attachments it's at least consistent with the order in the URL.

Wouldn't ticket:1:comment:1 make more sense? It would be much easier to copy /ticket/1#comment:1 from the URL bar and replace / and # with : than to reorder the parts.

[Ryan J Ollos]

Replying to anonymous:

(Here on trac.edgewall.org comment:1:ticket:1 doesn't work?)

I recall cboos explaining this issue in a ticket when I raised a similar point, and that a database upgrade step would be needed to fix the issue. I cannot find the comment at this time.

(Actually WikiFormatting only mentions: ticket:1#comment:1?)

See TracLinks page for extensive documentation.

A similar case is attachments: attachment:ticket:216:report.patch​

That's the old way of creating attachment links, see TracLinks#attachment:links.

But the orderings seem inconsistent:

• realm:parent-realm:parent-id:id (attachment:ticket:216:report.patch​)

This form is deprecated.

• realm:id:parent-realm:parent-id (comment:3:ticket:12597)

This is the form consistently used.

• parent-realm:parent-id#realm:id (ticket:1#comment:1)

This form works because you are linking to a heading on the page for ticket #1, consistent with a link such as wiki:TracGuide#Introduction.

The ordering is realm:id:parent-realm:parent-resource. That ordering is recommended, even for attachment links in which the old style still works.

[anonymous]

Ah nice. Wow, and the new way is already 10 years old. Thanks for the explanation!

[anonymous]

(Here on trac.edgewall.org comment:1:ticket:1 doesn't work?)

I recall cboos explaining this issue in a ticket when I raised a similar point, and that a database upgrade step would be needed to fix the issue. I cannot find the comment at this time.

#11816 maybe.

[Ryan J Ollos]

Replying to anonymous:

(Here on trac.edgewall.org comment:1:ticket:1 doesn't work?)

I recall cboos explaining this issue in a ticket when I raised a similar point, and that a database upgrade step would be needed to fix the issue. I cannot find the comment at this time.

#11816 maybe.

Yes, that's the one.

[Ryan J Ollos]

Edited WikiFormatting@122 and TracLinks@99.