Opened 15 years ago
Closed 15 years ago
#8833 closed defect (worksforme)
Cannot create query filter for custom field
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | report system | Version: | 0.11.1 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I added a custom field to my ticket:
[ticket-custom] test_one = requirement test_one.label = Requirement test_one.format = plain
The field is accessible in my ticket type but I can't create a query filter for it. If I try to add a query filter for this custom field using the combo box, nothing happens. If I add a query filter for an existing ticket field (eg Severity), a new filter is created.
Attachments (0)
Change History (6)
follow-up: 2 comment:1 by , 15 years ago
comment:2 by , 15 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Replying to stodge@…:
I should point out that due to scheduling and resourcing issues we can't upgrade our ennvironments to the latest version of Trac. Hence the use of 0.11.1.
Well, ok, but how do you expect us to fix the issue for you if you remain at 0.11.1?
AFAIK, custom queries work fine with custom fields in current 0.11-stable, so I'm afraid you'll have to update at some point. Please reopen if you can reproduce the issue with a recent version (0.11.5 or 0.11-stable).
comment:3 by , 15 years ago
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
Reproduced on 0.11.5 on my laptop.
comment:5 by , 15 years ago
It's still working here for all the standard field types. What kind of field type is "requirements"? It's certainly not in Trac core. Shouldn't you rather use:
[ticket-custom] test_one = text <---- field type test_one.label = Requirement test_one.format = plain
as specified on TracTicketsCustomFields?
comment:6 by , 15 years ago
Resolution: | → worksforme |
---|---|
Status: | reopened → closed |
Oh that's embarassing. I didn't even realise I had "requirement" as the type. I changed it to "text" and of course it works.. Oops! Thanks
I should point out that due to scheduling and resourcing issues we can't upgrade our ennvironments to the latest version of Trac. Hence the use of 0.11.1.