Opened 14 years ago
Closed 14 years ago
#8771 closed enhancement (duplicate)
Implement commenting on changes in Trac timeline
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | timeline | Version: | none |
| Severity: | normal | Keywords: | |
| Cc: | interstellar.condition@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
It would be nice to comment on changes in timeline. Maybe for some changes it would be redundant (tickets), but it would be very useful for changesets.
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.
Here comes timeline commenting. 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.
Attachments (0)
Change History (3)
follow-up: 2 comment:1 by , 14 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 14 years ago
I wasn't aware, thanks.
Replying to cboos:
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.
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.