Ticket #2961 (new enhancement)
Opened 6 years ago
Last modified 14 months ago
custom comment fields
| Reported by: | Ryan@… | Owned by: | jonas |
|---|---|---|---|
| Priority: | normal | Milestone: | next-major-0.1X |
| Component: | ticket system | Version: | 0.9.4 |
| Severity: | normal | Keywords: | time tracking tracobject |
| Cc: | ryan@… | ||
| Release Notes: | |||
| API Changes: | |||
Description
I'd like a function similar to TracTicketsCustom, but for comments.
I'm looking to integrate time tracking into Trac to eliminate some double entry, but unlike all the folks at #710, I'd like my "hours spent" field to be on the comment, so we can track who is putting in the time when, and not just have one field on the ticket everyone keeps updating.
Attachments
Change History
comment:1 Changed 6 years ago by ryan@…
- Keywords time tracking added
comment:2 Changed 6 years ago by anonymous
- Cc ryan@… added
comment:3 Changed 5 years ago by sid
comment:4 Changed 5 years ago by cboos
- Keywords tracobject added
- Milestone set to 2.0
No, I don't think so (well, at least not in a clean way).
(Developement Notes)
I have to think about having metadata for changes...
Now that I think about it, what I wrote about the comment in TracDev/Proposals/DataModel#ResourceChangeHistory can't be done without an indication that the comment is to be treated specially, labeled as a property sticking to the change, not as a changing property of the resource.
It's the same kind of distinction in Subversion, between a property and a revision property.
comment:5 Changed 5 years ago by ryan@…
My apologies, I forgot about this ticket completely. My company ended up writing a plug-in to accomplish my specific hours-tracking needs: TimingAndEstimationPlugin
I still think having generic custom comment fields would be good for extensibility, but the specific need I was looking to fill has been filled.
comment:6 Changed 22 months ago by cboos
- Milestone changed from 2.0 to unscheduled
Milestone 2.0 deleted
comment:7 Changed 14 months ago by cboos
- Milestone changed from unscheduled to next-major-0.1X
See GenericTrac#History.



Can this be accomplished with a plugin?