Edgewall Software
Modify

Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#12616 closed enhancement (worksforme)

Support ticket:1:comment:1 links?

Reported by: anonymous Owned by:
Priority: lowest Milestone:
Component: ticket system Version:
Severity: trivial Keywords:
Cc: Branch:
Release Notes:
API Changes:

Description

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:

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.

Attachments (0)

Change History (5)

in reply to:  description ; comment:1 by Ryan J Ollos, 3 years ago

Resolution: worksforme
Status: newclosed

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:

This form is deprecated.

This is the form consistently used.

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.

comment:2 by anonymous, 3 years ago

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

in reply to:  1 ; comment:3 by anonymous, 3 years ago

(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.

in reply to:  3 comment:4 by Ryan J Ollos, 3 years ago

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.

comment:5 by Ryan J Ollos, 3 years ago

Last edited 3 years ago by Ryan J Ollos (previous) (diff)

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.
to as closed The owner will be changed from (none) to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.