[Trac-tickets] Re: [The Trac Project] #1456: Combine tickets/changesets in timeline

[The Trac Project]

#1456: Combine tickets/changesets in timeline
----------------------+-----------------------------------------------------
       Id:  1456      |      Status:  new                     
Component:  timeline  |    Modified:  Thu Apr 21 05:16:41 2005
 Severity:  normal    |   Milestone:                          
 Priority:  normal    |     Version:  devel                   
    Owner:  jonas     |    Reporter:  ludde                   
----------------------+-----------------------------------------------------
Comment (by cboos):

 All this might become quite complex, for a not so obvious benefit:
  * what if you only filter in tickets in your timeline?
  * what if the ticket is reopened, and closed once again the same day
    (without a comment too :))
    How do you know which event should be ''merged'' with the changeset?

 About the relationship:
  * Using a sentence like {{{this closes #YYY}}} would only create
    a cross-reference, from the changeset in which that comment
    was made, to the referenced ticket.
    The semantic would be informal, and could be understood by
    looking at the context (which, in that case, would be the full
    sentence, because of its brevity).
  * Establishing a __real__ relation  would require a special wiki
    notation, for avoiding ambiguities, like those:
    * {{{one might think that this changest closes #yyy, but no.}}}
    * {{{Closes #yyy, really, uh? No Way!}}}
  * An example of such syntax would be:
    * {{{This <<closes>> #yyy}}} (like in [1354])
    * {{{This --closes-- #yyy}}} (which I currently prefer)
  * Even with this explicit syntax, it will not be obvious
    to find a way to trigger the close action at the
    appropriate time...
    For instance, what would happen if in {{{trac-admin}}}
    I do a {{{xref}}} command (i.e. rebuild all the cross-references)?
    Would the ticket be closed again?

 Note that currently there's no way to create a relation from a
 TracObject involving 2 other Trac objects.
 It's always something written in the source object that
 creates a relation to a referenced object.

-- 
Ticket URL: <http://projects.edgewall.com/trac/ticket/1456>
The Trac Project <>