Edgewall Software

Changes between Initial Version and Version 1 of Ticket #8771


Ignore:
Timestamp:
Oct 23, 2009, 2:45:03 PM (15 years ago)
Author:
Christian Boos
Comment:

Are you aware of #2035?

I think the idea of "commenting timeline events" should translate to "commenting on resource changes", on the resource themselves provided they allow to do such comments.

Adding that capability to more (all) resources is indeed one of the ideas motivating the GenericTrac approach.

There wouldn't be any duplication of commenting feature for the tickets, and, as you mentioned it, when viewing a changeset or anything else that has been commented upon, you'd like to have a way to see that such comments exist.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #8771 – Description

    initial v1  
    22Maybe for some changes it would be redundant (tickets), but it would be very useful for changesets.
    33
    4 For example, someone user changes some code in changeset [3333]. You you don't understand why he did it, but it's just a little question, you don't want to make a new ticket just for that question. If you send him an email, some other potentially interested users would not see your conversation.
     4For example, someone user changes some code in changeset ![3333]. You you don't understand why he did it, but it's just a little question, you don't want to make a new ticket just for that question. If you send him an email, some other potentially interested users would not see your conversation.
    55
    66Here comes timeline commenting.
    7 Of course this would require changes in other parts of Trac, for example in [changeset:3333 changeset view], where all comments related to that changeset should be displayed.
     7Of course this would require changes in other parts of Trac, for example in ![changeset:3333 changeset view], where all comments related to that changeset should be displayed.