#13004 closed defect (fixed)
Reserved Names for custom fields are not documented
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | not applicable |
| Component: | ticket system | Version: | 1.2 |
| Severity: | minor | Keywords: | documentation |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
The list of reserved names for custom fields should be documented on the TracTicketsCustomFields page, as was already suggested in 1449#comment:1.
I just wanted to create a custom field named "order" and wondered why it didn't work.
Attachments (0)
Change History (7)
comment:1 by , 6 years ago
| Owner: | set to |
|---|---|
| Status: | new → assigned |
comment:2 by , 6 years ago
| Owner: | changed from to |
|---|
comment:3 by , 6 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
follow-up: 5 comment:4 by , 6 years ago
Thank you to whoever made the change.
Just one more question: Will this change be automatically included in the next release? If not, could someone please make sure that it gets added to the documentation that will be installed as well.
comment:5 by , 6 years ago
Replying to Joachim Mairböck <j.mairboeck@…>:
Just one more question: Will this change be automatically included in the next release? If not, could someone please make sure that it gets added to the documentation that will be installed as well.
comment:6 by , 6 years ago
One caveat, probably doesn't need to be documented:
Selects like milestone and version are only reserved if they have options. For example, if you delete all milestones, you can use milestone as a custom field.
comment:7 by , 6 years ago
| Keywords: | documentation added |
|---|---|
| Milestone: | → not applicable |
Replying to j.mairboeck@…:
Anyone can modify wiki pages on this site. Could you please add documentation about the reserved names?