Bug #332
output field "recur_ind" not valid?
| Status: | Closed | Start: | 11/30/2009 | |
| Priority: | Normal | Due date: | ||
| To: | Paul Beckingham | % Done: | 100% |
|
| Category: | core | Spent time: | 1.00 hour | |
| Target version: | 1.8.5 - PAUL | Estimated time: | 1.00 hour | |
Description
howdy, messing around with some stuff and decided to try "recur_ind" and failed.
task help indicates that recur_ind should be a viable field. But a stripped down output filter tells me:
Unrecognized column name: recur_ind
the filter:
report.test-recur.description=test recur_ind
report.test-recur.columns=id,recur_ind,description
report.test-recur.labels= id,recur_ind,description
report.test-recur.filter=status:pending
am I doing something wrong or is recur_ind not actually a valid field?
(running 1.8.2 on mac. search on "recur_ind" did not find any prev issues.)
- tcyun
History
Updated by Paul Beckingham 276 days ago
- Category set to core
- Status changed from New to Assigned
- To set to Paul Beckingham
- Target version set to 1.8.5 - PAUL
- Estimated time set to 1.00
Charles, the 'recur_ind' column is missing from a critical place in the code. Good catch. Thank you.
Updated by Paul Beckingham 275 days ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
It's worse than I thought. The name "recur_ind" is wrong - the real name is "recurrence_indicator", and is implemented, but not documented. Similarly, "tag_indicator" is implemented but not documented.
Charles, consider upgrading to 1.8.4, or 1.8.5 when we release it next week.
Updated by t charles yun 274 days ago
yup, running the full form of the name works on my side. hooray!
I'll update to 1.8.5 when i see the announcement.
As always, thanks for the info.
- Charles