#13007 closed defect (fixed)
Using "added", "changed" and "removed" as custom fields, query results always are highlighted
Reported by: | Jun Omae | Owned by: | Jun Omae |
---|---|---|---|
Priority: | normal | Milestone: | 1.0.17 |
Component: | query system | Version: | |
Severity: | minor | Keywords: | |
Cc: | Branch: | ||
Release Notes: |
Use |
||
API Changes: | |||
Internal Changes: |
Description (last modified by )
Instead, _added
, _changed
and _removed
should be used because custom field cannot be started with _
.
See:
Attachments (0)
Change History (6)
comment:1 by , 7 years ago
Description: | modified (diff) |
---|
follow-up: 6 comment:2 by , 7 years ago
comment:3 by , 7 years ago
Milestone: | next-dev-1.3.x → 1.0.17 |
---|---|
Owner: | set to |
Status: | new → assigned |
Proposed changes in [aea4b2cb4/jomae.git] for 1.0-stable. I couldn't find uses of the 'removed'
.
comment:5 by , 7 years ago
Release Notes: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
Thanks. Committed in [16577] and merged in [16578-16579].
comment:6 by , 7 years ago
Replying to Ryan J Ollos:
TracTicketsCustomFields@37 should be updated after this issue is resolved to indicate that the fields are not reserved for Trac 1.0.17+. Actually, they aren't really reserved even for Trac < 1.0.17, so I'm not sure I agree with the edit.
Reverted edit in TracTicketsCustomFields@38.
TracTicketsCustomFields@37 should be updated after this issue is resolved to indicate that the fields are not reserved for Trac 1.0.17+. Actually, they aren't really reserved even for Trac < 1.0.17, so I'm not sure I agree with the edit.