#716 closed defect (invalid)
ID value instead of string value displayed for custom radio/select properties
Reported by: | Christopher Lenz | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ticket system | Version: | devel |
Severity: | normal | Keywords: | custom properties |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
When using TracTicketsCustom to add a custom property of type select or radio, the value of the property as displayed in the ticket info table is not the human-readable string value of the selected option, but rather the integer ID of the selected option.
Attachments (0)
Change History (3)
comment:1 by , 20 years ago
comment:2 by , 20 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Maybe this is a misunderstanding on my side, or the sample configuration on TracTicketsCustom is wrong. Apparently you can set the value to the string value of the option that should be selected by default. Setting no default value also has the desired effect.
We need to improve the documentation on custom ticket properties, but I think this ticket is actually invalid. Sorry for the spam.
I'm slightly wrong about this: It appears that if no value was set for the ticket (for example, because the custom property was added after the ticket was created), the value displayed for the property is the integer value assigned to the property in
trac.ini
.After the custom property has been set, the value is displayed correctly.