following a recent post, I create a new specific post about the following reflexion :
the filter list " Show" contains a lot of filters, especially for date filtering, and custom find tasks filters.
But why put in this list, the filters 'Selected tasks' and 'flagged tasks'? It is restrictive. Indeed :
* I can filter on category (for example) then use the filter selected tasks
* But I cannot filter on "task due by today" then use the filter selected tasks, because they are in the same list...
According to me, these 2 filters "selected tasks" and "flagged tasks" should be put in a new single filter combobox, in order to also be used in combination with the 'Show' filter.
And if this new filter combobox could remains enable even in case of custom find task filter, this would be great and useful.
I hope this feature can be feasible...
Thank you Dan.
For what it is worth, I have always found it a little logically strained to combine the date range filters with other attributes or statuses, such as all, complete, incomplete, selected, flagged.
It has never really caused me any issues though in the way I use TDL.
What I mean is that the date range filters are useful for finding tasks within a date range. Attribute filters are useful for finding tasks with a particular attribute (e.g. flagged or completed status). By combining these in the one filter, means flexibility is lost. I understand the 'Show' filter is a useful compromise, as it is a useful way of bringing up common views. IMHO it isn't logically 'pure' though, and means certain views aren't possible.
I want all flagged tasks due by the end of the month. By using the existing show filters I can only get all tasks due by the end of the month. I can't specify to see only the flagged ones in that date range. Similarly if you wanted to see all completed tasks in the date range (for reporting purposed for instance). You can use sorting to help though.
I am not sure this needs 'fixing' though, as we have the 'Find Tasks' functionality. This not only allows for more control over date ranges, but a wide variety of additional attributes can be included in the query you build. And when we can save a set of custom views/queries, all will be well. At that point, I will probably mainly use self created filters. And that is also why I would be keen to be able to remove the current built in ones.
PS: The functionality that the filter bar remains active when a custom filter is applied would be great. It could mean that you don't need to create a unique filter for, say, every member in the team...
I fully agree with this detailed explanation! It is exactly what i think. But your english is better than mine
However, I don't agree with the conclusion when you say That find task filter is the solution. Find task filter allows more control, Yes, but the 'selected tasks' filter is not possible via the find task functionality... And sometimes uses the find task filters is not so user friendly than the standard filters ( i need to modify my search Filter in ordre to have exactly what i want)
So IMHO, a little Fix / improvement in order to separate date filters from the others (uncompleted, selected, flagged, etc...), would be à good thing. And this "new" filter should remain enabled even in case of custom find task filter.
The selected task filter can be useful if you have a tasklist with several "topics" with several related tasks.
For example one parent "TECHNICAL", one other "BUSINESS".
Sometimes, I want to focus on the TECHNICAL part of the tree, and export related tasks (in html), for sending result to the technical user who don't care about business tasks.
So, regarding my request in this post, I need indeed to first filter, in order to see for example the current tasks of the week, then I want to focus on a specific part of the tree.
Thanks for the explanation. I can now see the usefulness if you can then see the children of the selected task. For exporting, I have just used the selected task option in the dialog - after selecting the appropriate tasks manually in the tasklist.
Saved 'finds' automatically added to filter droplist.
Great. Thank you very much.
One little bug crept in:
1. Enable 'view>show filter bar'.
2. Create a new custom field / column (Data type: Date); Attribute label (not column title) = 'Work On'
3. Create a new tasklist with four tasks
4. Make sure that one task has a due date (2012-Nov-23) and a 'work on date' (2012-Nov-20).
5. Create a new filter (Due Date relative - occurs on or before - t+7 and 'Work On Relative - occurs on or before - t+7) Save the filter (name: Testfilter)
6. Apply the filter (the find tasks window disappears).
Only one task should be visible in task tree view now (the task with the dates).
The filter bar shows: 0) Testfilter (Find tasks filter).
7. Change the filter to: A) All tasks
The task tree view shows now 4 tasks.
8. Go to the menu 'view>filter'. Choose '0) Testfilter (Find tasks filter)'.
The task tree view shows only one task as expected (the task with the dates).
9. Go again to the menu 'view>filter' and choose 'A) All tasks'. Press 'OK'.
The bug shows immediately:
ToDoList doesn't change the filter to 'All tasks'. The filter bar still shows: 0) Testfilter (Find tasks filter)
P.S. Thanks that it is possible now to move the attributes up and down.
While using/testing the 6.6 Dev Release, I had something strange happen: all of the due dates, start dates, statuses, categories, etc. blanked (disappeared) (for no reason) for all the sibling sub-tasks to the one that was hilighted. This was a bunch of tasks (over 300) in a parent task called "Main Tasks". After saving the TDL file and looking at it in wordpad, all of that stuff WAS really gone from the tasks. The actual choices for category, status, etc. WERE still in the TDL file (at the bottom) I'm not sure what I was doing at the time, but I restored a backup and it happened again (not sure what I did to cause it again - seemed to actually happen by itself)! I had to go back to the latest official version (6.5.8), because this was my actual tasklist that I use at work. I just wanted to let you know that this happened - might be another bug that crept into THIS version, because it never happened before (on other versions)