Opened 8 years ago
Last modified 8 years ago
#12252 closed defect
Incorrect initialization of new custom fields in existing tickets. — at Initial Version
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | 1.2 |
| Component: | ticket system | Version: | 1.0.2 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
When adding a custom field, it is possible to set what the default value should be when a new ticket is created, For existing tickets that do not yet have this value, the field seems to default to the first value (I have a 'select'-type variable). I would have expected it to be set to the same default value as for a new ticket. Is this expected behavior? I really would like all existing tickets to have the default value for this field.
It has been confirmed that this same behavior exists in the current trunk release.
Note:
See TracTickets
for help on using tickets.
