Opened 5 years ago
Last modified 5 years ago
#13133 closed defect
Do not add ticket change entry for default value of new ticket custom field — at Initial Version
| Reported by: | Ryan J Ollos | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.3.6 |
| Component: | ticket system | Version: | |
| Severity: | normal | Keywords: | custom fields |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Adding a new custom field, such as:
[ticket-custom] checkbox = checkbox checkbox.value = 0
results in a ticket change entry the next time an existing ticket is updated.
I'd like to discuss if it makes sense to skip adding the ticket_change table entry when the ticket custom field has a default value.
Issue raised in gdiscussion:trac-users:Kind9BaSR4Q.
Note:
See TracTickets
for help on using tickets.
