Ability to filter issue subtasks in issue form
|Target version:||Candidate for next major release|
It would be interesting to see the filters in a task and its subtasks
#8 Updated by Daniel Felix over 4 years ago
- Target version set to Candidate for next major release
This seems to be realy interesting to the community.
What do you think about my idea at #12860?
This could be solved by adding some filter by parent task which provides: 1.filter by parent task id is equal to
2.filter by parent task id is not equal to
3.filter by parent task id is not null (has parent tasks)
4.filter by parent task id is null (no parent tasks)
What do you think about this?
#10 Updated by Jiří Křivánek over 4 years ago
As you closed my issue as the duplicate of this one, I am copying my request inside - just to be completely sure...
And yes, if I understand your logic in post 8 hereby then your solution should work to me... thank you...
Jiří Křivánek wrote:
- Add support for filtering tasks also by the parent task ID.
- It should support
- Any exact value (as entered).
- Empty/not empty (i.e. only subtasks or only top level parent tasks).
- Matching and NOT matching.
- The management in my company where I established the Redmine is multi-level.
- Higher level manager enters the overall task on the project, containing the list of feature requirements.
- Lower level manager makes a specification and plans the works by creating a lot of sub-tasks for the above entered parent task.
- The higher level manager needs the custom view of tasks on the project where only the top-level tasks are visible.
#16 Updated by Mikhail Sviridov about 4 years ago
May be it will be better to fold/unfold tasks to allow user to expand only interesting tasks to access it's subtasks? If someone wants to see all the tasks and it's subtasks visible in the issue list it can be done by setting a tick "Expand all". It can be the setting for each project or for each user or global.Another way is to switch between list and hierarhical views of issues.
So the same operations will be different for these views:
- will sort all the issues in list view regardless of it is subtask or not
- will sort on each level (1st level tasks are sorted first, then 2nd level tasks inside the group made by it's parent tasks)
- will filter from all the issues in list view
- will filter from all the issues, but the result will be in form of:
filtered tasks (those are before A by sorting) A -> filtered subtasks of A (those are before B by sorting) -> B (has it's ranges of each field collected from subtasks) -> filtered subtasks of the B -> filtered subtasks of A (those are after B by sorting) filtered tasks (those are after A by sorting)
About list view
It is already implemented - so I don't need to do any comments here.
About hierarhical view
If it is very complex to implement and may be it is useless in most cases so you can perform operations (sort, filter) on the 1st level tasks only. To do sorting or filtering of subtasks of some task you should go into the task and inside it's subtasks list perform suitable operations again. So task have to have the same widget for subtask as issues page of the project or the issues list of the project have to have the title of the path "A -> B -> C" like wiki pages have.
Feel free to question me if something is unclear (probably, my english is dirty).