now it is possible to define to what a chainable applies for - this is used e.g. to separate filters for entries and filters for issues
git-svn-id: https://dev.finn.de/svn/cockpit/branches/reporting_merge@1273 7926756e-e54e-46e6-9721-ed318f58905epull/6827/head
parent
de8d8ac289
commit
2744f7bd1f
@ -1,5 +1,6 @@ |
||||
class CostQuery::Filter::DueDate < CostQuery::Filter::Base |
||||
date_operators |
||||
join_table Issue |
||||
applies_for :label_issue |
||||
label :field_due_date |
||||
end |
||||
|
@ -1,5 +1,6 @@ |
||||
class CostQuery::Filter::StartDate < CostQuery::Filter::Base |
||||
date_operators |
||||
join_table Issue |
||||
applies_for :label_issue |
||||
label :field_start_date |
||||
end |
||||
|
@ -1,4 +1,5 @@ |
||||
class CostQuery::Filter::Subject < CostQuery::Filter::Base |
||||
join_table Issue |
||||
applies_for :label_issue |
||||
label :field_subject |
||||
end |
||||
|
Loading…
Reference in new issue