Feature #6118
closedFilter by parent task or subtasks
Added by Xagyg Wulf over 16 years ago. Updated over 11 years ago.
Description
There doesn't seem to be an option to use "parent task" as a filter. I want to be able to select parent task as a filter and say "Parent Task is null" - so that I get all top-level issues (as well as issues without any children).
Files
| 6118-add_parent_issue_id_filter_to_issue_query.patch (543 Bytes) 6118-add_parent_issue_id_filter_to_issue_query.patch | Felix Schäfer, 2014-10-16 18:54 | ||
| rm6118-add_parent_issue_id_filter_to_issue_query-trunk_r13697.diff (2.94 KB) rm6118-add_parent_issue_id_filter_to_issue_query-trunk_r13697.diff | Mischa The Evil, 2015-02-13 07:19 |
Updated by Xagyg Wulf over 16 years ago
Actions
#1
Whoops - strike the bit in brackets "(as well as issues without any children)".
This is what I meant:
I want to be able to select parent task as a filter and say "Parent Task is null" - so that I get all top-level issues.
Updated by Sepp _ over 16 years ago
Actions
#2
+1
Updated by Jeffrey Jones over 16 years ago
Actions
#3
+1 This would be a hugely useful feature for things like the Gantt chart where we want an overview.
Updated by Anders Fältros about 16 years ago
Actions
#4
+1 Really would like to have this!
Updated by Ewan Makepeace about 16 years ago
Actions
#5
+1
We have added a patch to sum all the estimated issues on the page, all the issues returned by the query and also those in each group when grouped. Parent tasks are causing us to double (or triple) count some hours as they report the sum of all their child tasks (which may also be in the same list). Even with a filter on Parent Task (which I support) I still have a problem - could there be a 'Has Child Tasks' filter as well perhaps?
Updated by Emmanuel Toche about 16 years ago
Actions
#6
+1
Updated by Sylvain Guimond about 16 years ago
Actions
#7
+1
Updated by Charlie Chen almost 16 years ago
Actions
#8
+1
Updated by Martin Denizet (redmine.org team member) over 15 years ago
Actions
#9
My users don't like sub-tasking because they feel like it's making things more complicated and messy than before.
I think a "Is Parent" filter would really help them!
+1
Updated by David Andrews over 15 years ago
Actions
#10
+1 please.
Updated by Ruedi Silvestri over 15 years ago
Actions
#11
+1 also a patch would be much appreciated.
Updated by Terence Mill over 15 years ago
Actions
#12
+1
Updated by Lucas CORBEAUX about 15 years ago
Actions
#13
+1, such a filter would be really useful.
Updated by Terence Mill about 15 years ago
Actions
#14
+1
Updated by Etienne Massip about 15 years ago
Actions
#15
- Category set to Issues
Updated by Matthias Neubert about 15 years ago
Actions
#16
+1 seems that there will be some progress regarding this issue, can you determine for which version number this is planed?
regards
Matthias
Updated by Mischa The Evil about 15 years ago
Actions
#17
This feature was first requested via issue #5728. It was created by the UX-Team after UXTeamMeeting1 (see their meeting minutes, under "Core Challenges Observed with Subtask Feature:", number 2).
I've just closed #5728 as a "duplicated by" of this issue since most of the (relevant) discussion has taken place here (as suggested by Colan Schwartz).
Updated by Mischa The Evil about 15 years ago
Actions
#18
Updated by Bartosz Cisek almost 15 years ago
Actions
#19
+1
Updated by Gokay Gok almost 15 years ago
Actions
#20
+1
Updated by Paweł Maruszczyk over 14 years ago
Actions
#21
+1
Updated by Alexander Menshchikov over 14 years ago
Actions
#22
+1
Updated by Tomas K about 14 years ago
Actions
#23
+1
Updated by Hugo Zambotti about 14 years ago
Actions
#24
+1
Updated by Florent Fievez about 14 years ago
Actions
#25
+1
Updated by Fabrício Ferreira de Mendonça about 14 years ago
Actions
#26
+1
Updated by Josh Hansen about 14 years ago
Actions
#27
+1
Updated by Daniel Felix almost 14 years ago
Actions
#28
Updated by Thomas Lmx almost 14 years ago
Actions
#29
+1
It seems to be the most important feature for my project !
Updated by David Robinson almost 14 years ago
Actions
#30
+1
Updated by Dominik Follmann almost 14 years ago
Actions
#31
Thomas Lmx wrote:
+1
It seems to be the most important feature for my project !
same for us.
Updated by Daniel Felix almost 14 years ago
Actions
#32
Reference also #9992-8
Updated by Alexey Efimov almost 14 years ago
Actions
#33
+1 I'm interested in this feature also.
Updated by Sylvain Just almost 14 years ago
Actions
#34
+1 this feature will be very usefull for me too.
If anybody is interested, I also made a patch for display the parent subject and/or ID in email subject notification.
This information allow project manager to create template task with generic sub-tasks and copy it for recursives task.
Notifications by mail make more sense when subtask subject depends of parent subject.
Note : when task is just created, parent subject is unknown... so I display parent id instead of.
diff -r 64316d392708 -r 0f36159c4d63 app/models/mailer.rb
--- a/app/models/mailer.rb Tue Jan 22 16:06:10 2013 +0100
+++ b/app/models/mailer.rb Tue Jan 22 16:06:55 2013 +0100
@@ -43,9 +43,15 @@
@issue_url = url_for(:controller => 'issues', :action => 'show', :id => issue)
recipients = issue.recipients
cc = issue.watcher_recipients - recipients
+ #s = "[#{issue.project.name} - #{issue.tracker.name} ##{issue.id}] (#{issue.status.name}) "
+ s = "[#{issue.project.name} - "
+ s << "#{issue.tracker.name} " if (issue.tracker.id != 4)
+ s << "##{issue.id}] (#{issue.status.name}) "
+ s << "##{issue.parent_issue_id} > " if issue.parent_issue_id
+ s << "#{issue.subject}"
mail :to => recipients,
:cc => cc,
- :subject => "[#{issue.project.name} - #{issue.tracker.name} ##{issue.id}] (#{issue.status.name}) #{issue.subject}"
+ :subject => s
end
# Builds a Mail::Message object used to email recipients of the edited issue.
@@ -65,8 +71,11 @@
recipients = issue.recipients
# Watchers in cc
cc = issue.watcher_recipients - recipients
- s = "[#{issue.project.name} - #{issue.tracker.name} ##{issue.id}] "
+ s = "[#{issue.project.name} - "
+ s << "#{issue.tracker.name} " if (issue.tracker.id != 4)
+ s << "##{issue.id}] "
s << "(#{issue.status.name}) " if journal.new_value_for('status_id')
+ s << "#{issue.parent.subject} - " if issue.parent
s << issue.subject
@issue = issue
@journal = journal
You can also patch your project to display parent subject instead of tracker and ID in issues list :
diff -r 70ce4d70b7e1 -r 61345a556b62 app/helpers/application_helper.rb
--- a/app/helpers/application_helper.rb Tue Jan 22 16:12:26 2013 +0100
+++ b/app/helpers/application_helper.rb Tue Jan 22 20:10:39 2013 +0100
@@ -64,10 +64,13 @@
# link_to_issue(issue, :truncate => 6) # => Defect #6: This i...
# link_to_issue(issue, :subject => false) # => Defect #6
# link_to_issue(issue, :project => true) # => Foo - Defect #6
+ # link_to_issue(issue, :title => subject) # => This is the subject: Defect #6
+ # # if 'id' or nil => default behavior
#
def link_to_issue(issue, options={})
title = nil
subject = nil
+ if options[:title] == nil || options[:title] == 'id'
if options[:subject] == false
title = truncate(issue.subject, :length => 60)
else
@@ -82,6 +85,18 @@
s << h(": #{subject}") if subject
s = h("#{issue.project} - ") + s if options[:project]
s
+ elsif options[:title] == 'subject'
+ subject = issue.subject
+ if options[:truncate]
+ subject = truncate(subject, :length => options[:truncate])
+ end
+ tracker = "#{h(issue.tracker)} ##{issue.id}"
+ s = link_to subject, {:controller => "issues", :action => "show", :id => issue},
+ :class => issue.css_classes,
+ :title => tracker
+ s = h("#{issue.project} - ") + s if options[:project]
+ s
+ end
end
# Generates a link to an attachment.
diff -r 70ce4d70b7e1 -r 61345a556b62 app/helpers/queries_helper.rb
--- a/app/helpers/queries_helper.rb Tue Jan 22 16:12:26 2013 +0100
+++ b/app/helpers/queries_helper.rb Tue Jan 22 20:10:39 2013 +0100
@@ -72,7 +72,7 @@
when 'FalseClass'
l(:general_text_No)
when 'Issue'
- link_to_issue(value, :subject => false)
+ link_to_issue(value, {:subject => false, :title => 'subject'})
else
h(value)
end
Updated by André Schloemp over 13 years ago
Actions
#35
+1 we need this feature
Updated by Vito Marolda over 13 years ago
Actions
#36
+1
Updated by Sergio Tendero over 13 years ago
Actions
#37
+1
Updated by loic Le Gallou over 13 years ago
Actions
#38
+1 (display should include indirect subtasks in order to see the full branches related to a top parent task)
Updated by Artem Beloglazov over 13 years ago
Actions
#39
+1
Updated by Jeffrey Clark about 13 years ago
Actions
#40
Patch in #10828 should resolve this issue.
Updated by Toshi MARUYAMA about 13 years ago
Actions
#41
- Related to Feature #10828: Request multiple distinct values including issue id, parent_id, root_id added
Updated by Maxime Vez over 12 years ago
Actions
#42
+1
Updated by Laurent Dairaine about 12 years ago
Actions
#43
+1
Updated by Felix Schäfer about 12 years ago
Actions
#44
- File 6118-add_parent_issue_id_filter_to_issue_query.patch 6118-add_parent_issue_id_filter_to_issue_query.patch added
Here is a patch that adds a filter for parent task on the issue list.
Updated by Mischa The Evil about 12 years ago
Actions
#45
- Related to Feature #13054: Add the ability to filter issues on parent task. added
Updated by Luis Ferrao about 12 years ago
Actions
#46
It's been 4 years and innumerable similar requests, this feature is as basic as it gets, what's the hold up?
Updated by Vjacheslav Ryzhov almost 12 years ago
Actions
#47
Luis Ferrao wrote:
It's been 4 years and innumerable similar requests, this feature is as basic as it gets, what's the hold up?
subscribe to the issue
Updated by David Marín Carreño almost 12 years ago
Actions
#48
+1
Updated by Baatar Sukhbaatar almost 12 years ago
Actions
#49
+1
Updated by Igor Pellegrini almost 12 years ago
Actions
#50
+1
Any planned roadmap that could include this feature?
Would really improve my (and others) workflow.
Thanks.
Updated by Daniel Felix almost 12 years ago
Actions
#51
Our company uses many issues with many parent tasks. This feature would greatly improve our work with redmine, as we could filter all "master" issues. This would be really great to see this in the next release.
Updated by Mischa The Evil almost 12 years ago
Actions
#52
- File rm6118-add_parent_issue_id_filter_to_issue_query-trunk_r13697.diff rm6118-add_parent_issue_id_filter_to_issue_query-trunk_r13697.diff added
- Assignee set to Jean-Philippe Lang
- Target version changed from Unplanned backlogs to Candidate for next major release
A while ago I started a test of the patch Felix posted in #6118#note-44, therefor I started writing a solid test to back up the rather small code change.
I just finished extracting a patch (using git diff on a local dev branch, so don't mind the SHA's) from the older VM (source:/trunk@13697) I was working on, which includes the change proposed by Felix (although slightly adjusted to match current code [the filter key double quoted, while single quotes work just as fine here]) and an additional test (QueryTest#test_filter_on_parent_task_id) which covers the availability of the filter for issue queries and tests the functionality of each of the operators that are available for integer type filters. With this patch applied (as said on source:/trunk@13697) all existing tests pass (mysql-only, without ldap, scm and ui), as so does the newly added test for this feature.
@Jean-Philippe: can you assess/review this feature and patch to see if it can still be included in 3.0.0? There is obviously a clear demand for this and the change seems rather small and oversee-able, especially now that it includes a test.
Updated by Sebastian Paluch over 11 years ago
Actions
#53
This is great feature but should be done as more complete and include filter by parent task, root task and is leaf. Those are all parent-child relations.
Updated by txemi M over 11 years ago
Actions
#54
+1
I am patching production with Felix's patch, I would love it included in next release.
Useful for views of root tasks or child tasks of given task.
Updated by Jaromír Rys over 11 years ago
Actions
#55
+1
Updated by Maik Lindner over 11 years ago
Actions
#56
+1
Updated by Florian ROBERT over 11 years ago
Actions
#57
+1
Updated by Go MAEDA over 11 years ago
Actions
#58
- Target version changed from Candidate for next major release to 3.1.0
I tested Mischa The Evil's patch on current trunk (r14300) and it works fine.
Could it be in Redmine 3.1.0?
Updated by Jean-Philippe Lang over 11 years ago
Actions
#59
- Subject changed from Filter by parent task to Filter by parent task or subtasks
- Status changed from New to Closed
- Resolution set to Fixed
Mischa's patch is nice and simple but it does not address all the posibilities requested here.
I've added 2 filters in r14304 to filter on parent and subtasks (these 2 filters can be combined):
- parent
- is XXX (=> lists child issues of XXX)
- contains XXX (=> lists descendant issues of XXX)
- none (=> lists root issues)
- any (=> lists subtasks)
- subtasks
- is XXX (=> lists the parent of XXX, maybe not so usefull)
- contains XXX (=> lists ancestors of XXX)
- none (=> lists leaf issues)
- any (=> lists parent issues)
Updated by Go MAEDA over 11 years ago
Actions
#60
Thank you very much for implementing this!
Updated by Sebastian Paluch over 11 years ago
Actions
#61
That is great, no more plugins!
The only option that seems to be missing under "subtasks" is ability to show issue hierarchy deep to some level. This is useful to see overall list of job to do for a project to some level of details. (#20129)
Updated by Colan Schwartz over 11 years ago
Actions
#62
Sebastian Paluch wrote:
The only option that seems to be missing under "subtasks" is ability to show issue hierarchy deep to some level. This is useful to see overall list of job to do for a project to some level of details.
Open another ticket for that (unless there is one already), and link to it from here. Let's not cloud this fixed issue.
Updated by Alex Petty over 11 years ago
Actions
#63
Jean-Philippe Lang wrote:
I've added 2 filters in r14304 to filter on parent and subtasks (these 2 filters can be combined):
Excellent!! Thanks Jean-Philippe!!
Updated by Regis Leneveu over 11 years ago
Actions
#64
This seems to be the solution for some user-requests in our company.
Could you explain - for the rest of us - HOW I could create a filter which shows a specific tasks an all his related subtasks in a hierarchy?
I just can't figure it ou.
Thanks, Régis
Updated by Toshi MARUYAMA over 10 years ago
Actions
#65
- Related to Feature #22147: Change "Related issues" label for generic grouped query filters added
Updated by Go MAEDA over 9 years ago
Actions
#66
- Has duplicate Feature #10763: REST-API: Please add "parent_issue_id" as filter for requests to filter out subtickets added
Updated by Mischa The Evil over 6 years ago
Actions
#67
- Related to Feature #33352: Enable inline issue autocomplete in issue id query filter fields added
Updated by Holger Just about 2 years ago
Actions
#68
- Related to Feature #6958: Query Subtasks added