Opened 11 years ago
Closed 11 years ago
#11210 closed enhancement (duplicate)
Custom fields with custom behaviour
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ticket system | Version: | |
Severity: | trivial | Keywords: | custom fields metric |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I would like tuo have a field where I can store a progress metric (such as the work done today) in order to produce a report where I can analyze how much the estimated work differs from the real work. But if I want to add a value, for example 8 for today and tomorrow I would do the same (8), the Trac cannot sense the change (value 8 equals value 8), perhaps using a checkbox (which has the same kind of problem). I would like to force the update (insert of a new record with the custom field) into the ticket_change table. I'm pretty sure it is not possible just using custom fields.
Attachments (0)
Change History (2)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
But what changed? If you want to record the fact that you did some work but at the same time your estimation of remaining work stays the same, then you should rather record two different quantities instead of trying to force a "change event" for a value that stays the same.
Anyway, it's closely related to the discussions in #1084 (see my summary at the end of that ticket if you want a quick read ;-) ).