ticket summary type release owner status created modified _description _reporter 5456 Wiki formatting is not properly displayed in referenced ticket defect 0.11 new 2009-07-01T19:54:12+02:00 2020-05-06T01:55:40+02:00 "I added the following comment to one of my tickets: --- 1. Complete the following tickets. 1. Ticket #39 1. Ticket #54 1. Ticket #55 1. Ticket #56 1. Merge all development work from version 0.1 into the trunk and destroy the development branches. --- The actual wiki markup is: {{{ 1. Complete the following tickets. 1. Ticket #39 1. Ticket #54 1. Ticket #55 1. Ticket #56 1. Merge all development work from version 0.1 into the trunk and destroy the development branches. }}} When I look at ticket `#55` I see exactly: {{{ This ticket has been referenced in ticket #66: ... Complete the following tickets. 1. Ticket #39 2. Ticket #54 3. Ticket #55 4. Ticket #56 1. Merge all development work from version 0.1 into the trun... }}} The issues here are: 1. The indentation of the comment in `ticket #55` not correct. 1. A linebreak has been added, which probably results in issue `#3`. 1. The list numbering is not correct. " Ryan J Ollos 6643 When a description is edited to reference a ticket, a tracback is not created enhancement 0.11 new 2010-02-16T07:34:04+01:00 2020-05-06T01:55:40+02:00 "Related to #6641, When a ticket is referenced in the description, a tracback is added. When the description is edited to add a reference to a ticket, a tracback is not added." Ryan J Ollos 6641 TracBacks should get comment using a query on the DB defect 0.11 new 2010-02-16T07:27:59+01:00 2020-05-06T01:55:40+02:00 "Currently, if a ticket comment is changed, the comment in not changed in the referenced ticket. Trac 0.12 allows comments to be edited. That makes the following feature even more important: Perhaps we can query the database to get the comment, using a macro inserted into the referenced ticket, rather than copying the ticket comment from the reference to referenced ticket." Ryan J Ollos 6639 TracBack does not need to be inserted when ticket is already referenced in a log message containing multiple ticket references enhancement 0.11 new 2010-02-16T05:31:36+01:00 2020-05-06T01:55:40+02:00 "If a log message references two tickets, e.g. ticket `#100` and ticket `#200`, then the `trac-post-commit-hook` inserts the log message into ticket 100 and ticket 200. TracBacksPlugin then inserts a message into ticket 100 saying it was referenced in ticket 200, and vice-versa. We should make TracBacksPlugin smart enough to know when a reference has already been inserted into a ticket so that we don't get duplicate log messages inserted into tickets." Ryan J Ollos 3105 Trac-backs should function between projects (Trac instances) enhancement 0.11 new 2008-05-30T04:07:00+02:00 2020-05-06T01:55:40+02:00 it would be a nice feature to have tracbacks between projects or even between different instances so long as intertrac linking was functional. Jeff Hammel 6638 The tracback should contain a reference to the ticket AND comment # enhancement 0.11 new 2010-02-16T04:29:32+01:00 2020-05-06T01:55:40+02:00 As shown in the example, TracBacksPlugin#Example, the TracBacksPlugin only generates a reference to the referring ticket, not the actual comment. I'd like to see a direct link to the comment added to the ticket that is referenced. For example `comment:3:ticket:135`. This could be masked in the existing `#135` markup in the interest of keeping the tracback text concise. Ryan J Ollos 3606 Sidebar boxes for related tickets enhancement 0.11 new 2008-08-25T17:16:44+02:00 2020-05-06T01:55:40+02:00 "i would like to see all related tickets in a sidebar on each ticket. Maybe something like {{{

Related Tickets

}}} If any tickets had linked to this ticket, there could be another box for this information" Jeff Hammel 10396 Set up a functional test suite task 1.0 ejucovy new 2012-10-01T02:06:13+02:00 2020-05-01T06:51:13+02:00 "This plugin would benefit from a functional test suite; it should relatively easy to set up automated functional tests of its behavior, and the code involves several bits that address edge cases in fairly non-self-documenting ways. There are also a number of open feature requests and bug reports that involve fairly complex setups. Having a functional test suite would make the plugin more protected against regressions, more self-documenting, and easier to develop additional features and bugfixes against. A basic functional test suite should include tests for: * the plugin's basic behavior when commenting on an existing ticket with another ticket's reference * and when creating a new ticket whose description references another ticket * and when editing an existing comment (#6535) * and that the behavior is not triggered when including an apparent ticket reference inside a code block (#6846) crossed with conditions where: * the referenced ticket has a comment on it, and that comment is the latest change on the referenced ticket * and when referencing a ticket that has never been touched since creation, i.e. has no changelog entries (#9008) * and when referencing a ticket whose latest change is not a comment (#9743) Not all permutations of the above are necessarily needed, but also probably wouldn't hurt; I think it's worth formally distinguishing between demonstrations of the plugin's expected behavior (the first group above) versus tests of the conditions under which the behavior should work as expected (the second group above)" ejucovy 11244 Don't create trackbacks in select instances enhancement 1.0 ejucovy new 2013-07-25T17:37:32+02:00 2013-07-25T17:46:44+02:00 "The TracBacksPlugin is an extremely useful tool for automatic cross-referencing, but some other plugins handle cross-referencing on their own. This does not play well with this plugin, and can result in tickets being littered by automatically generated content. As an example, I also have the MasterTicketsPlugin installed. This allows tickets to have parent/child relationships. When I modify (for instance) ticket !#10 to indicate that it is a child of ticket !#5, a comment will be added to ticket !#10 indicating `Parent Tickets set to 5`. The MasterTicketsPlugin will then post a comment on ticket !#5 to say `Add a subticket #10`. Since this includes a ticket number, this triggers the TracBacksPlugin to add a comment on ticket !#10 to indicate that it was mentioned in another ticket. This sequence results in a redundant post to ticket !#10 that says the same thing as the previous post. This is only one example. Many plugins handle their own cross-references, and I expect that this problem would be seen for those plugins as well. To resolve this, I recommend adding a configuration option that allows a user to specify a regular expression (or list of regular expressions) to ignore. If a comment that would normally trigger the creation of a tracback matches that regular expression, then the TracBacksPlugin would not create a trackback." Ben Allen 7439 [patch] If you delete a comment, tracbacks creates incorrectly-numbered comments in a ticket defect 0.11 new 2010-07-30T17:22:42+02:00 2020-05-06T01:55:40+02:00 "To reproduce: 1. Create a ticket with 2 comments (so you have comment 1 and comment 2) 2. Delete one of the comments (so you have comment 2, by itself) 3. Create a comment in another ticket where you get a tracback to the first ticket. It will be created as comment #2. " matt.caron@… 5457 [PATCH] After a TracBack reference is added, all subsequent comments are in italics defect 0.11 new 2009-07-02T02:42:21+02:00 2020-05-06T01:55:40+02:00 "After a !TracBack reference is added to a tickets comment list, all subsequent comments are in Italics. Seems like there is probably a problem with the wiki markup that is generated an inserted for the !TracBack reference, such as an unterminated pair single quotes. See attached screen capture. " Ryan J Ollos