View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
09596 | Feature requests | Import/Export | public | 2015-04-03 16:36 | 2016-01-20 09:11 |
Reporter | DenisChenu | Assigned To | |||
Priority | normal | Severity | feature | ||
Status | new | Resolution | open | ||
Summary | 09596: Export result : adding filter by "everyting" | ||||
Description | Actually export result can be filtered by
I like to have a way to export by:
| ||||
Additional Information | Think it can be great to extend export helper , and move the from/to is to core plugin | ||||
Tags | export | ||||
Bug heat | 2 | ||||
Story point estimate | |||||
Users affected % | |||||
parent of | 07971 | closed | DenisChenu | Add a "filter by attribute" when exporting token |
This can be done using a plugin to update $sFilter in loadSurveyResults |
|
The ->compare system is great too. One "column",one "value" Compare can use directly (in value) : <= , > etc ... (see in actual browse responses). And =: remove the partialMatch We just have lack of 'in array' on OR ability: but this one need:
A lot more of possibility for plugins ... but a lot of events happen |
|
I have a solution : i update the "export" action link toi use my own export system ..... |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2015-04-03 16:36 | DenisChenu | New Issue | |
2015-04-26 16:52 | DenisChenu | Relationship added | parent of 07971 |
2015-04-26 16:53 | DenisChenu | Tag Attached: export | |
2015-12-15 09:16 | DenisChenu | Note Added: 33918 | |
2015-12-15 09:53 | DenisChenu | Note Added: 33919 | |
2015-12-15 09:54 | DenisChenu | Note Edited: 33919 | |
2015-12-15 09:59 | DenisChenu | Note Edited: 33919 | |
2016-01-20 09:11 | DenisChenu | Note Added: 34292 |