443 Subtasking Hi there! First of all, let me gratulate for the project, it's an impressive job. I think there is an important issue that needs to be done and this is subtasking. I mean you can create more tasks under another task, and thus - you can see a tree-like representation in the browse issues page (you know, with expandable + and - signs) - also you can see this tree in the gantt chart (like in MS Project) - the parent task's done percentage is the sum of the subtasks' done percentages (or you can configure it in the options whether it should sum or not) - the parent task's deadline is the deadline of the last subtask - the parent task's spent time is the sum of the subtasks' spent times - the parent task's priority is the highest of the subtasks' priorties I hope you agree that this is an important feature and we can see it soon implemented. Keep coding, bye, Sly. h3. Patches and feedback needed to be reviewed/merged by Eric * http://www.redmine.org/issues/443#note-158 * http://www.redmine.org/issues/443#note-159 * http://www.redmine.org/issues/443#note-161 * http://www.redmine.org/issues/443#note-164 * http://www.redmine.org/issues/443#note-167 * http://www.redmine.org/issues/443#note-168 * http://www.redmine.org/issues/443#note-169 * http://www.redmine.org/issues/443#note-171 0 Fri Sep 21 15:05:00 +0200 2007 Wed Mar 03 23:29:47 +0100 2010 +1 - Would be very useful for my projects and many others I know would benefit from Redmine once this feature is there

+1 from me :)

+1 I think it will be quite useful feature. Regards, iGor.

I HOPE, TOO. And Subtasks are categorized such as 'analysis, design, implementation, test' on development issues. IMHO. Above categorized tracker is only assigned to subtasks.

This is a simple concept cord. - the parent task's done percentage is the sum of the subtasks' done percentages (or you can configure it in the options whether it should sum or not) - the parent task's start is the start of the first subtask - the parent task's due date is the due date of the last subtask - the parent task's spent time is the sum of the subtasks' spent times - the parent task's estimated time is the sum of the subtasks' estimated times - the parent task's priority is the highest of the subtasks' priorties But this does not function in the list and the Gantt chart.

@sunday walker: you should use the command svn diff to produce a uniq patch: so many files are difficult to handle to evaluate your work. Thank you.

Thank you for your advice. (Thomas Lecavelier) original http://redmine.rubyforge.org/svn/tags/0.6.3

issue #556 is a dup of this one.

original http://redmine.rubyforge.org/svn/tags/0.6.3 issue-index-csv : add outline for ms-project

original http://redmine.rubyforge.org/svn/tags/0.6.3 issue-index : add outline

One thing about subtasks. Now is very uncomfortable process for create subtasks. It will be very nice, if can select parent task on create new. And link to create new task from add relations block in ticket view.

+1 I very like it. I see there is corresponding patch. When it will be merged with current trunk? :(

+1 Extremely needed. I am using sundaywalker's patch to 0.6.3 version. It's pretty good and useful. However it contains a mistake which I managed to repair but I am not eager to publish as: - it is not my enhancement and I am not a ruby developer - bufix is very straightforward and only a workaround, as I am not a ruby developer The bug lies in make_outline method which recursively falls into infinite loop in some cases. So I am not able to upgrade to 0.7 as subtasking is critical functionality for me. And it seems to me that applying 0.6.3 patch isn't very sensible. I hope that 0.8 version will contain it in standard. Cheers Radek

Duplicates #443.

Please, add this to version 0.8

+1. This would be very useful for organizing tasks.

+1 It would be a good feature to have

I'm currently working on a patch that adds this feature to Redmine 0.7.1. It uses some concepts introduced by sunday_walker (like implementing parent relations through Redmine's default issue relations mechanism) and supports viewing issues in a tree with expandable + and - signs on the list issues page. It should be ready in one or two months.

@Giovanni Junior It would be great! I can't wait to test it... Could you, please, try to make it compatibile with sunday_walker's model? Cheers Radek

+ 1 This would be very useful to have especially because we use issues as mini projects (manufacturing order) and it would be useful to group several tasks (engineering, purchasing etc. ) together

+1. Please, add this to 0.8 release.

+1 +1 +1 I hope you know that we love you guys P.S. Really need this :)

Hello guys My patch isn't pretty ready yet, but has enough features to be tested. It's intended to be applied to Redmine 0.7.3, but should be easily applied to 0.7.1 and 0.7.2 as well. It may not meet some of the requirements listed above, as it was developed according to my client's needs. Redmine's built-in issue relations are used to tie subtasks to their parent tasks, as did sunday walker. When creating/editing issues, only issues marked as "potential parents" are showed in the "child of" field. To get subtasks in your Redmine, # apply the patch; # add _contract.png_ to _REDMINE_HOME/public/images_; # in Redmine's root directory, execute _ruby rake db:migrate_. Please note that so far this patch is intended for testing purposes only. As said before, the work has not been completed yet. By the way, any suggestions are pretty much welcome. Giovanni

(+ 1...) In the 3rd step above, the command _ruby rake db:migrate_ should be replaced with _ruby rake db:migrate RAILS_ENV="production"_ (or _RAILS_ENV="development"_, or _RAILS_ENV="test"_). New version of the patch attached! @Radek Borecki I guess my patch supports the subtasks you created in version 0.6.3. Check it out!

I have adopting this patch to trunk version of Redmine. I also done some changes in it. Here is the list of changes: * removed field 'potential parent' completely; * added a new field 'child of' with auto completion facility; * changed view on Roadmap and Version of parent & children; * added some validation related to subissues; * added tests for subissues behaviour.

Aleksei Gusev wrote: > I have adopting this patch to trunk version of Redmine. I also done some changes in it. Here is the list of changes: > * removed field 'potential parent' completely; > * added a new field 'child of' with auto completion facility; > * changed view on Roadmap and Version of parent & children; > * added some validation related to subissues; > * added tests for subissues behaviour. As of today, December 9th , I cannot find this patch from trunk yet. Could you please review? Lam

Lam Ngo wrote: > Aleksei Gusev wrote: > > I have adopting this patch to trunk version of Redmine. I also done some changes in it. Here is the list of changes: > > * removed field 'potential parent' completely; > > * added a new field 'child of' with auto completion facility; > > * changed view on Roadmap and Version of parent & children; > > * added some validation related to subissues; > > * added tests for subissues behaviour. > > As of today, December 9th , I cannot find this patch from trunk yet. Could you please review? > > Lam Maybe, my English so bad and you did not understand me. ;] This patch is not in trunk (I am not a Redmine official developer), this patch *can* be applied on trunk sources, not more. ;] I have attached the next version of the patch. I also have to note, that the patch requires autocomplete plugin (git://github.com/rails/auto_complete.git).

This is a great patch! Any comments from the dev's as to this patch will be integrated in an upcoming version?

Boudewijn van Liempd wrote: > This is a great patch! > > Any comments from the dev's as to this patch will be integrated in an upcoming version? Thanks for the feedback. I did not receive any comments from the developers, but I am going to support this at least as separate patch, that can be applied to trunk.

Aleksei Gusev wrote: > Lam Ngo wrote: > > Aleksei Gusev wrote: > > > I have adopting this patch to trunk version of Redmine. I also done some changes in it. Here is the list of changes: > > > * removed field 'potential parent' completely; > > > * added a new field 'child of' with auto completion facility; > > > * changed view on Roadmap and Version of parent & children; > > > * added some validation related to subissues; > > > * added tests for subissues behaviour. > > > > As of today, December 9th , I cannot find this patch from trunk yet. Could you please review? > > > > Lam > > Maybe, my English so bad and you did not understand me. ;] This patch is not in trunk (I am not a Redmine official developer), this patch *can* be applied on trunk sources, not more. ;] > > I have attached the next version of the patch. I also have to note, that the patch requires autocomplete plugin (git://github.com/rails/auto_complete.git). sorry, my bad. Installed the patch and it works! Thanks!

How about showing the parent - child relationship on the Gantt chart?

Lam Ngo wrote: > How about showing the parent - child relationship on the Gantt chart? This feature is planned, but I do not know when I am going to make that.

+1 any progress here?

+1 This would be very beneficial.

+1 It's a great idea.

I have attached the new version of subissues patch. Patch notes: * redesigning subissues layout; this includes new feature 'View options' which allow you to change view of the list issues; there are tree options for show parent now: - never show parents; - always show parents for every child issue; - organize by parent, which is means to group sorted issue by the same parent and show issue grey even when it not passed filter. * added a hook which sets 'Due to' date, when 'Target version' sets, but 'Due to' date is unset.

Sorry, patch is relatively big due to lang files. Here is the bziped version.

+1 Very important feature for software projects. Please consider adding it to 0.8.1 We are redmine's very happy users.

Please, Aleksei: Add your patch to a new issue in patch category, so it can catch the attention of official developers, and then add a link to this new issue.

Don't you know any plugins for Redmine to implement something similar to subtasks?

David Marín Carreño wrote: > Please, Aleksei: > > Add your patch to a new issue in patch category, so it can catch the attention of official developers, and then add a link to this new issue. I think the developers know about the patch. It seems like official team do not think that the patch is useful. Implementing this functionality as plugin is very hard. I am not sure that it is even possible. Sorry.

+1 vote from me as well. Our team of ~10 developers has recently started using Redmine and really like it. We practice scrum, however, and (for our purposes) the lack of a way to nicely group issues (into deliverables or stories) is one of the tool's few shortcomings (we migrated from XPlanner). Subtasking, if done in a way that allows us to track progress on the parent deliverable, would fill this need for us.

João Ribeiro wrote: > Please consider adding it to 0.8.1 It wouldn't be in 0.8.1 because it's a large change. It could be in a minor release (e.g. 0.9.0). See [[ReleaseManagement]] Aleksei Gusev wrote: > I think the developers know about the patch. It seems like official team do not think that the patch is useful. I've seen the patch and think it could be useful but the patch needs a few improvements before it can be integrated: * Don't upload compressed patches, it make anyone who wants to review download and uncompress it. Attach them as plaintext diff or patch files * There are a lot of extra files included in this patch that should be removed. Only modifications to the Redmine core and new files directly related to the feature should be included in the patch ** vendor/plugins/redmine_timesheet_plugin ** tmp/cache/.gitignore ** config/deploy.rb ** config/environments/warecorp_redmine.rb ** config/environments/warecorp_redmine_test.rb ** db/migrate/20081125140453_add_calendar_startday_pref.rb.rb Once the patch is corrected, it can be reviewed to see about being included.

This patch is also broken for trunk as of commit:2304 since Project#active_children got dropped and it depends on the auto_complete plugin

It is very very usefull and high priority feature! I hope the developers will be able to add this to the core soon. It will make redmine awesome

How applay this path (subissues.diff.bz2 ) on Windows? (version 8.0)

I have reviewed the patch file. The files not related to the core was deleted, The patch was tested on 2361 revision. Still needs auto_complete plugin. ;( I am going to fix that.

Please, tell me what else I should fix for including this patch to official version. Thanks in advance!

+1 as this would make Redmine match up much closer to our actual planning and work flow! PS: thanks to all the people working on this patch so far, appreciated.

It is the only thing, that Redmine doesn't have is respect to JIRA =)

Well, do you know if this patch can be applied on Windows platform? And if it can be applied - how it can be done? This feature is very important for us, redmine is very useful and comfortable tool for project management at all, but it's harder to plan / work with complex task by using only plain tasks structure :(

+1 We've just started using redmine in our project and we really need this feature implemented.

We really need this feature, too!!! I'm monitoring this ticket everyday by bookmarking this #443 issue, to see any progress. Please, add this patch to trunk..

+1 waiting for feature! It would be a great improvement after version 0.7.2 for me!

+1 It is a very useful feature for project management. Will this be added to 0.9.0? When can we hope to have it in SVN?

Another +1 and a question - is it possible to sponsor this issue, i.e. donate money to increase its development priority?

+1 definitely something we need, thanks very much for the work so far

+1 We are working with Aleksei under this feature more then 2 months, more then 1 month this patch installed on our production server. More than 30 peoples that working in our company and uses subtasking. So, I can easy say "+30"

I don't think that many people would use this feature..... just kidding. :) Last I heard, Aleksei Gusev was going to add the auto_complete plugin. Does this still need to be done? http://www.redmine.org/issues/show/443#note-56

Aleksei, I appreciate your effort to maintain this patch but adding this feature to the core is not planned for now. The main problem I see with this patch is the implementation of the tree. The IssueRelation model was not designed to be used for that. Lots of queries and recursions could be saved by using some kind of nested trees. And I don't see any test :-(

+1 would be a very welcome feature

Hey Eric, As I know Aleksei work on this. Eric Davis wrote: > I don't think that many people would use this feature..... just kidding. :) > > Last I heard, Aleksei Gusev was going to add the auto_complete plugin. Does this still need to be done? http://www.redmine.org/issues/show/443#note-56

Hey Jean-Philippe, I understand that current code of subtasking looks not finished. Originally we used Mr. sunday's code. But we are working on development process (Aleksei was not taking part in ruby development before). So we (company) allocated resources for Redmine development. Besides we have beta version of Redmine plugin for document encrypting (check http://github.com/hron/redmine_encrypted_document_plugin/tree/master). So, we are interested in including this patch in trunk, seeing a lot of comments in this thread - you probably interested too. If you can correct way of our development - it will be great, in this case we can receive skills and finish patch according to your perspective. Thanks, Stas. Jean-Philippe Lang wrote: > Aleksei, I appreciate your effort to maintain this patch but adding this feature to the core is not planned for now. > > The main problem I see with this patch is the implementation of the tree. The IssueRelation model was not designed to be used for that. Lots of queries and recursions could be saved by using some kind of nested trees. > And I don't see any test :-(

Thanx guys, u r the best!

+1 The lack of subissues is what is keeping us from switching from Jira. Also, this must be the most requested issue in the Redmine issue tracker. Please consider helping Aleksei test and refine his subissue patch so that it could enter trunk easily.

I am new to ruby and redmine I have just managed to install redmine (0.8.2) I would like to apply this patch on my installation Please let me know what should I do to apply this patch on my configuration. Best Regards Imran Sheth

This feature also very useful for tracing requirements... What is the current status? Thanks!

Can we conclude that this is a very much wanted feature, together with #1011... ;) I don't really like my mailbox to be flooded with '+1' mails, but if that is normal on this tracker I'll unwatch this item.

+1 I agree with the previous poster, this is a much wanted feature together with #1011 :) From my experience tasks are completed much easier, faster and happier :) when they are smaller rather than they are bigger :) Therefore this feature will give us a brilliant ability to divide large tasks to smaller sub-taks and thus achieving results more quickly. Moreover, sometimes large tasks stay uncompleted just because we do not know how to start implementing it and we think that this virtually impossible to complete task. For example like this issue. Dividing such tasks to smaller steps would really help to implement them. Jean-Philippe Lang wrote: > The main problem I see with this patch is the implementation of the tree. The IssueRelation model was not designed to be used for that. Lots of queries and recursions could be saved by using some kind of nested trees. > And I don't see any test :-( Maybe you could move towards with small steps in this direction? I think for starters almost everyone would be satisfied with an "ability to add subtasks in a click" and an ability to see all sub-tasks in a specified ticket same as we see related taks. I'l try to show you what I mean. Please see this image, below is displayed a list of subtickets for a current ticket and a process of adding a subticket: !http://crystalrich.com/uploadi/picture_20090328164746328.png! This is a base functionality for subtickets feature I think... No tree required! I think that displaying of tickets as tree in "Issues" section may wait for future versions (or another good idea is just to make option "display only master tickets"). I understand that implementation of this feature without "tree" is not as nice and holistic as a complex decision, but we will get a simple feature to divide tickets. And this is much better then nothing. P.S. I'd like to say thank you to all people who developed and maintained this project. I'm using it for only one day and I love it for its usability and gracefulness!

dear Redmine developers my regrets but: 1. the Feature is very needed. 2. i agrees to be bug tester. 3. feature is opened in 2007's, and now is the 2009. 4. may be your need a donate - i agree... 5. same in Russian - мне одназначно не хвататет этой функциональности и я даже готов за это доплатить. сколько можно откладывать "фичу" - за два то года можно было реализовать. я всё понимаю, но сколько можно прибавлять "плюсиков".

I'm working on this issue again. I updated Aleksei Gusev's code to Redmine 0.8.2 and started changing the models to implement hierarchy using acts_as_tree instead of IssueRelations. When I finish the work on the models and update views accordingly, I will release a patch so that you can start giving feedback. Feel free to contact me: giovannijunior.a.t.gmail.d.o.t.com.

It's not done yet (and still uses some core hacks) but I've gotten some basic subtasking working in a plugin. This is *not* supported by Redmine.org or myself yet. If anyone wants to take my branch and run with it, I'd be happy to help them get it refined and released. http://github.com/edavis10/redmine_story_decomposition/tree/2081-subtasks P.S. Please don't complain about this being in a plugin and not in the core. Creating, testing, and supporting the feature as a plugin is the *very best* way to get working code into the core.

So, here is the version of my patch implemented with awesome_nested_set plugin. I do not recommend using this version on the any production, because I plan to implement subtasking as plugin in near future (maybe on this weekend...). I added this patch here to get feedback from Jean-Philippe and Eric. Please, take a look at this and let me know if I am not in the right direction. I very appreciate your help. Thanks in advance!

Aleksei Gusev wrote: > I do not recommend using this version on the any production, because I plan to implement subtasking as plugin in near future (maybe on this weekend...). > Well, very interested in this implementation! Thanks for you

This is uber-needed feature, also it is vital for Redmine too. Shall we motivate developers to make a stable plugin with some donations? I'll talk to my boss today =) In Russian: Очень нужная фича, жизненно важная для самого Redmine. Может, действительно, стоит отправить несколько донейтов с просьбой реализовать эту фичу? Я поговорю сегодня с шефом =)

ivan s. wrote: > This is uber-needed feature, also it is vital for Redmine too. Shall we motivate developers to make a stable plugin with some donations? I'll talk to my boss today =) > > In Russian: Очень нужная фича, жизненно важная для самого Redmine. Может, действительно, стоит отправить несколько донейтов с просьбой реализовать эту фичу? Я поговорю сегодня с шефом =) Lightweight solution as a plugin that I have implemented for myself is publicated at http://www.redmine.org/boards/3/topics/4701#message-5724. For now only relations (parent->child) feature is implemented.

In Russian: Для себя решение данной проблемы (с подзадачами) я реализвоал в качестве плагина и опубликовал в ветке http://www.redmine.org/boards/3/topics/4701#message-5724, реализовано только управление и просмотр отношений задач друг с другом (как показано там на картинке).

+1 for integrating it into the current trunk. I think, this is a killer feature and should not end in a plugin! Please integrate it into the trunk.

I have finished inital version of this patch as a plugin for Redmine. I have concentrated in just migrate all features of this patch to plugin. The plugin has tests. It looks like it ready for testing. http://github.com/hron/redmine_subtasks/tree/master Due to switching from using issues_relations table to awesome_nested_set there is no way to see issues hierarchy in 'show' action for specific issue. I am going to add this feature soon. The plugin migrations support migration from a database patched with my previously patch. Just install trunk version of redmine, add this plugin, migrate it. The migrations should detect the situation of applied the #443 issue's patch and acts accordingly. Any suggestions and help is welcome!

I am willing to also make a donation to get this into the core. Let me know how much to get this into the core so I can stop the systems guys from arguing about this topic.

+1, i'm interested in this issue much.

Andrew Chaika's Ticket grouping plugin is another choice. !http://www.redmine.org/attachments/2151/issues-group-nested.jpg!

Aleksei Gusev wrote: > I have finished inital version of this patch as a plugin for Redmine. I have concentrated in just migrate all features of this patch to plugin. The plugin has tests. It looks like it ready for testing. > > http://github.com/hron/redmine_subtasks/tree/master ... > Any suggestions and help is welcome! This works nice on the latest SVN version, but not for the 0.8.4 or 0.8.3 stable version. How to make this work in these versions? Due to the new I18n structure it gives an error during the plugin migration: @uninitialized constant Redmine::I18n@ Any help is welcome!

Hans Kazan wrote: > Aleksei Gusev wrote: > > I have finished inital version of this patch as a plugin for Redmine. I have concentrated in just migrate all features of this patch to plugin. The plugin has tests. It looks like it ready for testing. > > > > http://github.com/hron/redmine_subtasks/tree/master > ... > > Any suggestions and help is welcome! > > This works nice on the latest SVN version, but not for the 0.8.4 or 0.8.3 stable version. > How to make this work in these versions? > > Due to the new I18n structure it gives an error during the plugin migration: > @uninitialized constant Redmine::I18n@ > > Any help is welcome! I want to have some time for stabilization of this plugin for trunk version. I have found some bugs recently. When I will finished fixing these issues I am going to add compatibility level for stable version. Thank you for the testing.

Aleksei Gusev wrote: > Thank you for the testing. I thank you for the time spent already on this nice plugin! We are now discussing to help the development of Redmine. And, amongst other nice new features, support this one. Some bugs/improvement: * the "show parents" option is not remembered as a selection and revert to the default (maybe convert this to a plugin setting?) * The estimated time is summed up as it should be from the sub tasks but the % complete and spent time is not totalized * Setting the % done or status or priority of the parent does not have any effect on the sub tasks An option to bulk edit these automatically or set them all to the same % complete would help Note: maybe would it be wise to create a separate entry for this new plugin? And even bette combine efforts to help this feature towards functionality of core 0.90

Hans Kazan wrote: > Aleksei Gusev wrote: > > > Thank you for the testing. > > I thank you for the time spent already on this nice plugin! > We are now discussing to help the development of Redmine. And, amongst other > nice new features, support this one. > > Some bugs/improvement: > * the "show parents" option is not remembered as a selection and revert to the default > (maybe convert this to a plugin setting?) It saves in query object (in session) as any other filter rules. So you can use standard way to save this setting. I actually can add setting for default value of this option. > * The estimated time is summed up as it should be from the sub tasks but > the % complete and spent time is not totalized > > * Setting the % done or status or priority of the parent does not have any effect on the sub tasks > An option to bulk edit these automatically or set them all to the same % complete would help Spent time totalizing works in slightly more interesting algorithm. % complete calculated based on "weights" of every subtasks. For example, one subtask which has duration (due_date - start_date) 4 days, and other 1 days, so even if second subtask has 100%, it only 20% of parent task. > > Note: maybe would it be wise to create a separate entry for this new plugin? > And even bette combine efforts to help this feature towards functionality of core 0.90 Maybe you are right, but everyone know issue #443. ;]

Aleksei Gusev wrote: > Maybe you are right, but everyone know issue #443. ;] There are some fairly compelling arguments for creating a Patch-issue with all the files. This is the feature request, and it could be fulfilled by several different patches. I would also make things a lot cleaner. Just refer to 443 and i'm sure some admin would create a nice relation. Just my €0.02

+1 but what is with the project Details/report pages?

I can't modify a issue Child'of attribute after creation. In log i found the following line: "WARNING: Can't mass-assign these protected attributes: parent_id" This is bug?

We know about this. We found a few bugs and now we are in fix mode. Wait for a while for a fixed version. Szabolcs Klement wrote: > I can't modify a issue Child'of attribute after creation. > In log i found the following line: > "WARNING: Can't mass-assign these protected attributes: parent_id" > This is bug?

+1 very important feature

It could be very good, if the plugin would worked with 0.8.4 version.

Anton Nepomnyaschih wrote: > It could be very good, if the plugin would worked with 0.8.4 version. This plugin works with 0.8.4. However, it is a work in progress and lacks lots of features. Will be in GitHub soon. @Radek Borecki and others Does anybody still need to migrate from _sunday_walker_'s model? If so, I could prepare instructions on how to do it.

Giovanni Junior wrote: > @Radek Borecki and others > Does anybody still need to migrate from _sunday_walker_'s model? If so, I could prepare instructions on how to do it. I appreciate that you remembered about me. Thanks! We're still using 0.7.x with a small number of modifications. We haven't upgraded yet, because there are no critical features in newer versions. sunday_walker's solution keeps working :) (with small modifications, which I've mentioned before). Currently we operate with 220 projects, more than 100 users and 15k+ issues. However, I can see 0.9 on the horizon, and as the project goes extremely well (thanks Jean-Philippe! and TEAM), I would like to persuade my IT dept. to upgrade to 0.8.5. And to your solution as a result. So, instructions on how to migrate would be very welcomed. Thank you very much.

Sorry... I forgot to mention that it depends on _auto_complete_ plugin (http://github.com/rails/auto_complete/tree/master). Just install _auto_complete_, run db:migrate:all or db:migrate:plugins and it should work.

steeven lee wrote: > Andrew Chaika's Ticket grouping plugin is another choice. > > !http://www.redmine.org/attachments/2151/issues-group-nested.jpg! this plugin works fine but i can't see how i can configure it in the options so that the parent task's done percentage iswould be the sum of the subtasks any idea??? thanks in advance

hi, I get the following error during installation. I typed command <pre>rake db:migrate_plugins RAILS_ENV="production"</pre> I get the following error. please help. I am using Redmine 0.8.4.stable rake aborted! no such file to load -- awesome_nested_set

If you talking about my plugin (redmine_subtasks), you have to use trunk version of Redmine. This plugin does not work with stable (0.8.x version). Henry Huang wrote: > hi, I get the following error during installation. I typed command > [...] > > I get the following error. please help. I am using Redmine 0.8.4.stable > > rake aborted! > no such file to load -- awesome_nested_set

We are using the latest version of your plugin and redmine_charts version .14 and redmine "Redmine 0.8.4.devel.2847". When we click on "Logged hours deviations" within charts, redmine crashes with this error: <pre> Processing ChartsDeviationController#data (for XXX.XXX.XXX.XXX at 2009-10-10 16:57:23) [GET] Parameters: {"project_id"=>"bgz", "action"=>"data", "controller"=>"charts_deviation", "range_in"=>"weeks", "range_steps"=>"10", "range_offset"=>"1"} NoMethodError (undefined method `-' for nil:NilClass): /vendor/plugins/redmine_subtasks/lib/redmine_subtasks/redmine_ext/issue_patch.rb:21:in `leaf?' /vendor/plugins/redmine_subtasks/lib/redmine_subtasks/redmine_ext/issue_patch.rb:205:in `estimated_hours' /vendor/plugins/redmine_charts/app/controllers/charts_deviation_controller.rb:39:in `get_data' /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.2.2/lib/active_record/base.rb:2049:in `each_with_index' /vendor/plugins/redmine_charts/app/controllers/charts_deviation_controller.rb:33:in `each' /vendor/plugins/redmine_charts/app/controllers/charts_deviation_controller.rb:33:in `each_with_index' /vendor/plugins/redmine_charts/app/controllers/charts_deviation_controller.rb:33:in `get_data' /vendor/plugins/redmine_charts/app/controllers/charts_controller.rb:85:in `data' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/base.rb:1253:in `send' [snip] </pre> Otherwise, this plug in is great - thanks.

We have the same problem, as Burt Culver has. We use version 0.8.5.devel.2939 undefined method `-' for nil:NilClass /opt/redmine-test/vendor/plugins/hron-redmine_subtasks-bfcac35/lib/redmine_subtasks/redmine_ext/issue_patch.rb:21:in `leaf?' /opt/redmine-test/vendor/plugins/hron-redmine_subtasks-bfcac35/lib/redmine_subtasks/redmine_ext/issue_patch.rb:224:in `due_date' /opt/redmine-test/app/models/issue.rb:267:in `duration' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/associations/association_proxy.rb:221:in `send' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/associations/association_proxy.rb:221:in `method_missing' /opt/redmine-test/app/models/issue_relation.rb:68:in `set_issue_to_dates'

Burt Culver wrote: > We are using the latest version of your plugin and redmine_charts version .14 and redmine "Redmine 0.8.4.devel.2847". When we click on "Logged hours deviations" within charts, redmine crashes with this error: > > [...] > > Otherwise, this plug in is great - thanks. Received a similar error today when testing a new plugin: Processing IssuesController#show (for 60.234.173.23 at 2009-10-19 08:33:47) [GET] Parameters: {"action"=>"show", "id"=>"7714", "controller"=>"issues"} Rendering template within layouts/base Rendering issues/show.rhtml Completed in 531ms (View: 374, DB: 138) | 200 OK [https://redmine.fishpond.co.nz/issues/7714] Starting Charts Plugin for RedMine Starting Messemger Plugin for RedMine RedmineMessenger: connecting ... Starting Subtasks plugin for RedMine Processing IssuesController#index (for 60.234.173.23 at 2009-10-21 08:46:14) [GET] Parameters: {"project_id"=>"bgz", "action"=>"index", "controller"=>"issues"} Rendering template within layouts/base Rendering issues/index.rhtml ActionView::TemplateError (undefined method `issue_content' for #<ActionView::Base:0x2b9a74f3c048>) on line #32 of vendor/plugins/redmine_subtasks/app/views/issues/_list.rhtml: 29: <%= issue_content( parent_issue, query, :unfiltered => true) %> 30: <% end -%> 31: <% end -%> 32: <%= issue_content( issue, query, :emphasis => ( emphasis_issues ? emphasis_issues.include?( issue) : false)) %> 33: <% end -%> 34: <% else -%> 35: <% parents_on_first_lvl = [] vendor/plugins/redmine_subtasks/app/views/issues/_list.rhtml:32 vendor/plugins/redmine_subtasks/app/views/issues/_list.rhtml:16:in `each' vendor/plugins/redmine_subtasks/app/views/issues/_list.rhtml:16 /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_view/helpers/capture_helper.rb:36:in `call' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_view/helpers/capture_helper.rb:36:in `capture' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_view/helpers/capture_helper.rb:129:in `with_output_buffer' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_view/helpers/capture_helper.rb:36:in `capture' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_view/helpers/form_tag_helper.rb:460:in `form_tag_in_block' /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_view/helpers/form_tag_helper.rb:39:in `form_tag' It could be that it isn't redmine_subtasks fault, but that is where the issue is happening.

Using this plugin for a few days now, i'm confused with a small thing. In the screenshot in this post : http://www.redmine.org/issues/443#note-120 i can see some + and - sign, to collapse and expand subtasks. But, i don't have them in my redmine, (like in the screenshot under). I'm using a slightly modified version of the Classic theme, but it doesn't work either with the Default or alternate themes. Is there something i missed (like another plugin or a css class, or a configuration options) ? Or is it normal :) ? Thank you. PS: I'm using these plugins : header template modification -> This plugin modifies the layouts/base view -> made by ourselves, but does not (or at least is not supposed to) affect the issues list. Charts Plugin Redmine Hudson plugin Redmine Newissuealerts plugin Subtasks plugin Redmine Task Board plugin Redmine Wiki Extensions plugin And, the screenshot under is taken from Chrome 3, but the view is the same with Firefox 3.5 and IE 7.

Jean-Baptiste RIGUET wrote: > Using this plugin for a few days now, i'm confused with a small thing. In the screenshot in this post : http://www.redmine.org/issues/443#note-120 i can see some + and - sign, to collapse and expand subtasks. But, i don't have them in my redmine, (like in the screenshot under). I'm using a slightly modified version of the Classic theme, but it doesn't work either with the Default or alternate themes. Is there something i missed (like another plugin or a css class, or a configuration options) ? Or is it normal :) ? Thank you. You use my plugin, redmine_subtasks. It does not have such functionality and I do not plan to implement this, I think that + and - is not useful thing. The screenshot you mentioned is of redmine_issues_group plugin.

Hello, i try to install the redmine_subtasks feature. i'm using latest svn-trunk of redmine. But: when i try to migrate database i get this error: <pre> redmine>rake db:migrate_plugins RAILS_ENV=production [...] Migrating redmine_subtasks... == IssuesRebuild: migrating ================================================ -- rebuilding left & right indexes rake aborted! An error has occurred, all later migrations canceled: Validation failed: Author can't be blank </pre> anyone any idea? Thanks Felix

Even if a parent issue has a due_date set, Issue.due_date seems to be overridden by subtasking plugin to return null for parent issues. The null value is, however, not detected in the database select. This causes a problem with the gantt charts. I'm using redmine trunk. Here is a stack trace: ActionView::TemplateError (You have a nil object when you didn't expect it! The error occurred while evaluating nil.<=) on line #181 of app/views/issues/gantt.rhtml: 178: @gantt.events.each do |i| 179: if i.is_a? Issue 180: i_start_date = (i.start_date >= @gantt.date_from ? i.start_date : @gantt.date_from ) 181: i_end_date = (i.due_before <= @gantt.date_to ? i.due_before : @gantt.date_to ) 182: 183: i_done_date = i.start_date + ((i.due_before - i.start_date+1)*i.done_ratio/100).floor 184: i_done_date = (i_done_date <= @gantt.date_from ? @gantt.date_from : i_done_date ) app/views/issues/gantt.rhtml:181:in `_run_rhtml_app47views47issues47gantt46rhtml' app/views/issues/gantt.rhtml:178:in `each' app/views/issues/gantt.rhtml:178:in `_run_rhtml_app47views47issues47gantt46rhtml' app/controllers/issues_controller.rb:371:in `gantt' app/controllers/issues_controller.rb:370:in `gantt' /usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service' /usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run' /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:95:in `start' /usr/lib/ruby/1.8/webrick/server.rb:92:in `each' /usr/lib/ruby/1.8/webrick/server.rb:92:in `start' /usr/lib/ruby/1.8/webrick/server.rb:23:in `start' /usr/lib/ruby/1.8/webrick/server.rb:82:in `start'

0.9 is almost out and I can't find this most hoped for feature in the feature list :-(

I have a feeling that this feature will be in 1.0 version

Andrew Chaika wrote: > I have a feeling that this feature will be in 1.0 version I can't see anything about subtasking in the roadmap for 1.0. Is it more than a feeling ? I have installed the plugin, but I am not feeling very comfortable about it since there is no easy way to fully uninstall plugins. So when (if ?) this comes to trunk, I don't know if the upgrade will be painful or not.

About your application's environment Ruby version 1.8.7 (i486-linux) RubyGems version 1.3.1 Rails version 2.1.2 Active Record version 2.1.2 Action Pack version 2.1.2 Active Resource version 2.1.2 Action Mailer version 2.1.2 Active Support version 2.1.2 Edge Rails revision unknown Application root /opt/redmine Environment production Database adapter mysql Database schema version 101 About your Redmine plugins My Effort plugin 0.1.0 Customer plugin 0.2.0 Redmine Vote plugin 0.0.2 Issue Due Date 0.1.0 Charts Plugin 0.0.14 Redmine Graphs plugin 0.1.0 Stuff To Do Plugin 0.3.0 Redmine Bugcloud plugin 0.0.2.1 Budget 0.2.0 Rate Plugin 0.1.0 Redmine Local Avatars plugin 0.0.2 Google Analytics plugin 0.2.0 Redmine Schedules plugin 0.4.2 Redmine Whining plugin 0.0.2 Redmine Taskjuggler plugin 0.0.2 Project Scores Plugin 0.0.1 Redmine Issues Group plugin 0.1.4 Redmine Question plugin 0.3.0 Redmine Code Review plugin 0.2.9.2 Redmine Status Updates 0.1.1 just downloaded the version available @http://www.redmine.org/wiki/redmine/Plugin_List#Subtasks-plugin when i try to nigrate the plugin i get: (in /opt/redmine-0.8.7) rake aborted! can't convert Hash into String /opt/redmine-0.8.7/vendor/plugins/gloc-1.1.0/lib/gloc.rb:190:in `iconv' /opt/redmine-0.8.7/vendor/plugins/gloc-1.1.0/lib/gloc.rb:190:in `load_localized_strings' /opt/redmine-0.8.7/vendor/plugins/gloc-1.1.0/lib/gloc.rb:189:in `each' /opt/redmine-0.8.7/vendor/plugins/gloc-1.1.0/lib/gloc.rb:189:in `load_localized_strings' /opt/redmine-0.8.7/vendor/plugins/gloc-1.1.0/lib/gloc.rb:188:in `open' /opt/redmine-0.8.7/vendor/plugins/gloc-1.1.0/lib/gloc.rb:188:in `load_localized_strings' /opt/redmine-0.8.7/vendor/plugins/gloc-1.1.0/lib/gloc.rb:175:in `each' /opt/redmine-0.8.7/vendor/plugins/gloc-1.1.0/lib/gloc.rb:175:in `load_localized_strings' /opt/redmine-0.8.7/config/initializers/30-redmine.rb:4 /opt/redmine-0.8.7/vendor/rails/activesupport/lib/active_support/dependencies.rb:503:in `load' /opt/redmine-0.8.7/vendor/rails/activesupport/lib/active_support/dependencies.rb:503:in `load' /opt/redmine-0.8.7/vendor/rails/activesupport/lib/active_support/dependencies.rb:355:in `new_constants_in' /opt/redmine-0.8.7/vendor/rails/activesupport/lib/active_support/dependencies.rb:503:in `load' /opt/redmine-0.8.7/vendor/rails/railties/lib/initializer.rb:484:in `load_application_initializers' /opt/redmine-0.8.7/vendor/rails/railties/lib/initializer.rb:483:in `each' /opt/redmine-0.8.7/vendor/rails/railties/lib/initializer.rb:483:in `load_application_initializers' /opt/redmine-0.8.7/vendor/rails/railties/lib/initializer.rb:149:in `process' /opt/redmine-0.8.7/vendor/rails/railties/lib/initializer.rb:97:in `send' /opt/redmine-0.8.7/vendor/rails/railties/lib/initializer.rb:97:in `run' ./config/environment.rb:20 /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require' /opt/redmine-0.8.7/vendor/rails/activesupport/lib/active_support/dependencies.rb:510:in `require' /opt/redmine-0.8.7/vendor/rails/activesupport/lib/active_support/dependencies.rb:355:in `new_constants_in' /opt/redmine-0.8.7/vendor/rails/activesupport/lib/active_support/dependencies.rb:510:in `require' /opt/redmine-0.8.7/vendor/plugins/redmine_whining/lib/tasks/whining.rake:30 /opt/redmine-0.8.7/vendor/rails/activesupport/lib/active_support/dependencies.rb:503:in `load' /opt/redmine-0.8.7/vendor/rails/activesupport/lib/active_support/dependencies.rb:503:in `load' /opt/redmine-0.8.7/vendor/rails/activesupport/lib/active_support/dependencies.rb:355:in `new_constants_in' /opt/redmine-0.8.7/vendor/rails/activesupport/lib/active_support/dependencies.rb:503:in `load' /opt/redmine-0.8.7/vendor/rails/railties/lib/tasks/rails.rb:7 /opt/redmine-0.8.7/vendor/rails/railties/lib/tasks/rails.rb:7:in `each' /opt/redmine-0.8.7/vendor/rails/railties/lib/tasks/rails.rb:7 /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require' /opt/redmine-0.8.7/Rakefile:10 /usr/lib/ruby/1.8/rake.rb:2149:in `load' /usr/lib/ruby/1.8/rake.rb:2149:in `raw_load_rakefile' /usr/lib/ruby/1.8/rake.rb:1897:in `load_rakefile' /usr/lib/ruby/1.8/rake.rb:1948:in `standard_exception_handling' /usr/lib/ruby/1.8/rake.rb:1896:in `load_rakefile' /usr/lib/ruby/1.8/rake.rb:1880:in `run' /usr/lib/ruby/1.8/rake.rb:1948:in `standard_exception_handling' /usr/lib/ruby/1.8/rake.rb:1878:in `run' /usr/bin/rake:28

To be honest, I don't think this will ever work. It seems like it's been about 2 years now, and one this plugin doesn't seem to ever have been stable and appears as though anytime anyone says anything about putting it into the core(which is where it belongs) they are told, use this plugin. Guess what this plugin is not stable does not work, and here we stand 2 years and still no clean way to do subtasks.

I've ported the redmine_subtasks plugin from Aleksei Gusev for 1.0. Issues can be made subissues of others. There is no technical limit on the depth though it could get confusing with deep hierarchies. Significant changes: * Issue list has a View Option which can organize the list into a hierarchy. * Issue details page will show a filtered list of the parent and subissues with full support for the right click context menu * When assigning subissues, a JavaScript search is used to find the target issue using the: issue id, subject, description, and notes. * Parent issues will total the estimates from child issue * Parent issues will use the last due date from it's child issues * Parent issues will calculate the % done based on it's child issues * Parent issues will inherit the latest Version from it's children Significant changes from the plugin: * Several performance optimizations including basic caching of calculated attributes and N+1 queries * Closing few private data leaks (security) I still have a few questions I'd like to get some feedback on before I'd be comfortable committing it to the core: * Does the way Parent issues inherit Versions look correct? * Should there be a separate permission for assigning subtasks? (it uses the Manage Issue Relations option now) There's a few more refactoring and performance optimizations I'd like to do but I'd rather wait until this is committed, otherwise it would take too much time to keep merging the core changes into the patch.

It's a huge patch. It needs intensive review and I'm afraid it won't be part of 1.0.

I'm afraid too. Sad new. Subissues it's a very important feature, as much as issue dependency. I'll keep waiting ... Eric, which is the right versión to patch with your patch file?

Jean-Philippe Lang wrote: > It's a huge patch. It needs intensive review and I'm afraid it won't be part of 1.0. I'm going to be direct here: not including Subtasks in 1.0 will be a huge mistake. Every day now I hear someone asking or complaining about Redmine not having subtasks. It would be a shame to push this feature back again with so many people wanting it and all of the work everyone has done to create a working patches for it (I'm counting 137 updates to this request, 79 watchers, and at least 3 plugins trying to implement it themselves with some crazy hacks). I've already spent over 40 hours in December to review and port the plugin from Aleksei Gusev to get the patch working with the core. It's not a perfect implementation but it's a solution people can use now and we can improve it over the next 6 months to 1.0.

Jean-Philippe Lang wrote: > It's a huge patch. It needs intensive review and I'm afraid it won't be part of 1.0. I think it worth it, specially because this a great feature, a really useful one I tried with the other option and this one is more solid, it could be improved in the usability , but without subtasking most of the modeled processes in redmine would be nearly imposible. Evenmore, this plugin has a good support from developer page (eric). I wonder if anyone that has it installed think that is unnecesary? it like internet ajax, everithing goes well without it until someone try it, the horizon got expanded

This improvement to Redmine would be fantastic, the ability to compose work at levels suitable to developers, but only report on levels suitable to project managers would simplify a common usage pattern of Redmine tremendously. In fact I first came to use redmine based solely on several agile plugins that provided this functionality (that sadly are no longer kept up to date.) In the 'open' issue tracking market no other option that I'm aware of solves this problem in an elegant fashion (trac, bugzilla etc.) having this built into the core of Redmine would be fantastic! +1 (In case you weren't sure!)

+1 In fact, one of my colleagues just asked me if it was possible (I answered "soonly, soonly...")

+1 I completely agree with Jean-Philippe in comment 138. This would make my life so much easier .. combining a simple summary task view with the ability to decompose into more granular activities and effectively treat tasks as mini projects. From the project management view this would be a huge benefit, and developers also love it as they can add their own implementation tasks without cluttering the overall picture .. Please let it be released!

+1 Definitely anticipating this one. And for whatever it's worth, I agree with Mr. Davis in comment 138 as well. In my opinion, this should be a 1.0 feature if possible. Keep it simple at the start, and build on it later. For every watcher and commenter, there is probably another like me who has been quietly waiting on it. (I just found this issue after being surprised it wasn't planned as a 1.0 feature.)

+1 I've never felt the need to post a comment on Redmine before, as we've been satisfied with about every aspect of it. But I agree with the recent comments. We have a plan to revamp our internal ticket and project management processes that we will implement as soon as this feature is added to the core. This is by far the most anticipated feature for us.

Eric Davis wrote: > I've already spent over 40 hours in December to review... Eric if you need a tester, bug-explorer - my 8 hours in the week for this task and for you

+1 I really don't want to repeat all the remarks concerning the importance of this feature. So, please, include it as soon as possible. Eric, I would like also to offer myself as a tester for this feature.

You're right, there's no need to repeat that. I know that this is a must have but I want it to be simple and robust and I don't think this patch can be committed as is. You know I spent a few hours on Redmine code too and I spend even more time on fixing bugs. So I'm just saying that this feature needs more work and I can't guarantee it will be part of 1.0.

Jean, clearly, this feature has a lot of people who are interested in working on it. Do you think it is possible to show us some guidelines in order to make this patch good enough to be added to the trunk?

Luiz Carlos Junior wrote: > +1 I really don't want to repeat all the remarks concerning the importance of this feature. So, please, include it as soon as possible. > > Eric, I would like also to offer myself as a tester for this feature. +1 I can also help test. The way that we work really needs a good subtask system. Templated subtasks would be great too, but I can set that up after the subtasks are working. [What I mean by templated subtasks, is that I have a number of standardized processes that need to be passed between a number of people for many of the requests that I have to get built. So I know the basic steps for types of tasks, and it would be great to select the type of task and have a tree of subtasks attached. That way none of the subtasks gets missed.]

This redmine subtasks plugin dont work at Redmine 0.9 version, I tried half day to make it works, without success. I am wondering why Redmine has not subtasks by default, its very usefull things for people that need to manage whole projects. Has anybody a way how to make it works for 0.9?

Would it be useful if I create a test site with this patch applied to let everyone try it out?

Eric Davis wrote: > Would it be useful if I create a test site with this patch applied to let everyone try it out? sure, thanks a lot.

Eric Davis wrote: > Would it be useful if I create a test site with this patch applied to let everyone try it out? Yes, please. Built against 0.9 preferably. -sh

Eric Davis wrote: > Would it be useful if I create a test site with this patch applied to let everyone try it out? Thanks a lot. Please update the url of test site.

Just a question : I have aleksei's plugin installed on redmine trunk (Redmine 0.8.7.devel.3076 for the moment). Is the patch fully compatible with the plugin ? Will I be able to just dump my databse, backup my "redmine/files" folder, reinstall redmine, apply the patch and restore my database and files ? Thanks !

Eric Davis wrote: > I've ported the redmine_subtasks plugin from Aleksei Gusev for 1.0. > Sorry to be so weak, but I've failed to apply this patch to various SHA's can anyone tell me what version of the source they would expect this patch to apply cleanly to (I've tried the HEAD of edavis10's git mirror, to various tag HEADS and even to points in time where I think the patch may have been created (the referenced from in the patch file I cannot find :( ) .. I assume I'm being thick so any help would be appreciated. thx.

ciaran jessup wrote: > Eric Davis wrote: > > I've ported the redmine_subtasks plugin from Aleksei Gusev for 1.0. > > > Sorry to be so weak, but I've failed to apply this patch to various SHA's can anyone tell me what version of the source they would expect this patch to apply cleanly to (I've tried the HEAD of edavis10's git mirror, to various tag HEADS and even to points in time where I think the patch may have been created (the referenced from in the patch file I cannot find :( ) .. I assume I'm being thick so any help would be appreciated. > > thx. Finally! Sorry for the previous message, if anyone else suffers similary in the future, this patch appears to apply (relatively) cleanly to 7193817deabe2ac2e5a067fa3674b2d1d3973450 on http://github.com/edavis10/redmine ;)

In case anyone is interested I've put-up a git branch with Eric's patch applied here: http://github.com/ciaranj/redmine/tree/sub_tasks Eric, there are a couple of issues with this branch, I'm not really sure how you want me to report issues, or whether to report them at all ? So far I've noticed: * Issue %Done is not aggregating (either when issue %done is specified by field or by status) * Making changes via the context menu in the 'Issues Hierachy' pane of an issue seems to remove it from the parent issue (haven't tied this down yet as a repro case.) * Changing the tracker on an issue created (but not yet saved) via the 'Add sub-issue' icon causes the 'child of' field to loose the pre-populated parent id. There are some enhancements that I think (personally at least) would be useful for production : * From a parent issue; being able to add a pre-existing child issue directly. * From a child issue; being able to reference a parent just by bug number (this may be implemented but I couldn't seem to get it to work and ended up using the search drop-down everytime) * From the search context-menu being able to set/un-set a parent relation of an issue(s) [this would help for moving issues between groups if the hierachy is being used for issue grouping (a common scenario I believe) * A constraints model to define which trackers can be children of other trackers (for example perhaps I'd like to be able to create 'Stories' which could never be the child of any other tracker and 'Tasks' which can *only* ever be children of 'Stories' I'm more than happy to do some work on this if you want, I've waited for this to drop into redmine core for as long as my team would let me, but now I've got team members trying to 'mock' this up using depends-on/blocked-by approaches which is far from elegant (the %done aggregation is what I'd really like, plus the roadmap views!) but I'll follow your lead on what you think we should do (we could perhaps continue to develop the approach in a branch to iron out further bugs [I appreciate your earlier reticence to do this, but the positive impact of this plugin/patch on the wider redmine community is fairly large I would say!] )

I've updated the most recent patch on this issue (Eric's) in the following manner: *Fixes* * Changes made to issues via the context-menu in either the hierarchy view or the issue search results no longer remove any 'parent-child' relationship. * When creating sub-issues if the tracker is changed the 'parent issue' is no longer lost *Significant/Contentious changes* * The behaviour of the %Done aggregation was initially un-clear to me, it seems that when your redmine is in a '%Done by issue status' world the aggregated %Done is calculated based on estimated start and due dates. For me (and I appreciate the possibility that this might not be the common case, although I think it may be) when I have my child issue %done configured by their statuses I wish to have the parent %Done to merely aggregate this up. I suspect a proper implementation allows some configuration of how aggregation occurs, however this patch changes the observed behaviour such that if you are in a Status==%Done world the aggregated %Done is now calculated solely on the children %Done(s) This patch applies 'cleanly' (there are some pre-existing whitespace issues in the previous patch) to the git commit with sha: 7193817deabe2ac2e5a067fa3674b2d1d3973450 (which is roughly speaking a 0.85 redmine version) on the official git mirror: git://github.com/edavis10/redmine.git I intend now to rebase my branch up to 0.91 and I'll also endeavour to provide the patch for that too. The outstanding wishes that Eric had previously stated are still there (as are mine) and I also am not sure how 'version association' should work meaningfully other than that this patch looks to be in very good shape :)

ciaran jessup wrote: > I've updated the most recent patch on this issue (Eric's) in the following manner: Please be aware that I've accidentally included a changed environment.rb file in that patch :( and sadly this configuration of redmine means that I can't remove/ammend my own attachments or even fix my own typos and formatting errors in my own comments, which given how cavalier I am is getting increasingly frustrating!!! :)

As previously promised a patch that applies cleanly to 0.9.1 . Hope it helps someone :)

hi, big fan of redmine, came across this plugin but it is all starting to become a bit confusing with all the updates and all ... First of all, I installed the plugin using git clone git://github.com/hron/redmine_subtasks.git vendor/plugins/redmine_subtasks, can somebody confirm that this is the correct location to get this plugin? Secondly, the description mentions "... you can see this tree in the gantt chart (like in MS Project", could somebody please post a picture of what that is suppose to look because I cannot see any tree in my GANTT. I attached 2 pictures to show you what I mean ... Cheers, Mark.

Mark Vilrokx wrote: > hi, > > big fan of redmine, came across this plugin but it is all starting to become a bit confusing with all the updates and all ... > > First of all, I installed the plugin using git clone git://github.com/hron/redmine_subtasks.git vendor/plugins/redmine_subtasks, can somebody confirm that this is the correct location to get this plugin? Starting to be confusing ;) The confusion arise because there are many different approaches to sub-tasking described in this thread of conversation. The plugin you've downloaded is, as far as I'm aware the most complete and up-to-date approach (there is also a separate alternative issue-grouping plugin mentioned in the thread) the most recent activity however was by Eric to integrate this plugin directly into the core of redmine, and because the patch has not (yet?) been accepted that has lead to some confusion as to which way to go, personally I prefer to follow the core for things that affect the db schema rather than use plugins, but for whatever reason it currently looks as though this feature won't make it into the core code base anytime soon so you may be better sticking to the plugin (but there are some subtle semantic differences between the above core patches, and the plugin implementations.)

What happens when you don't choose the sum option? From an Agile perspective, you only want to estimate tasks and you don't want to estimate subtasks. Pivotal Tracker uses a checkbox for a task. A task in Pivotal Tracker would be equivalent to a subtask in Redmine. A story in Pivotal Tracker would be equivalent to a task in Redmine. [[http://pivotallabs.com/users/dan/blog/articles/965-story-tasks-in-pivotal-tracker]]

Ricky Gomez wrote: > Pivotal Tracker uses a checkbox for a task. A task in Pivotal Tracker would be equivalent to a subtask in Redmine. > A story in Pivotal Tracker would be equivalent to a task in Redmine. > [[http://pivotallabs.com/users/dan/blog/articles/965-story-tasks-in-pivotal-tracker]] Definitely good comment

Stas Belov wrote: > Ricky Gomez wrote: > > Pivotal Tracker uses a checkbox for a task. A task in Pivotal Tracker would be equivalent to a subtask in Redmine. > > A story in Pivotal Tracker would be equivalent to a task in Redmine. > > [[http://pivotallabs.com/users/dan/blog/articles/965-story-tasks-in-pivotal-tracker]] > > Definitely good comment Personally I just use a couple of custom fields on my 'story' trackers to track the story/points & business value of the story and use the %Done as an aggregate of the task %done where I treat tracker status as a fixed '%done' this gives me (I think) a reasonable middle ground to know roughly how 'done' a particular task is but does mean I have nothing that aggregates up the story points anywhere. (You can name your trackers whatever you want so task can be a story, subtask a task whatever you wish)

ciaran jessup wrote: > As previously promised a patch that applies cleanly to 0.9.1 . Hope it helps someone :) There is a slight problem with this patch - it breaks "shared versions" in 0.9.x branch. It is not possible to set shared version in Add / Edit Issue. Also fixes offering "closed" versions to user in this Add / Edit form.

The current subtasks patch displays whole subtask hierarchy the issue is part of. This patch to jessup's patch from 161 changes _subissues_list.rhtml so that only # ancestors of issue selected are displayed # only direct children of selected issues are displayed This significantly helps if you have large ( 40+ in several levels ) number of subtasks. And also it helps to make the issue relations easier to read. You see who is parent ( and it's parent, etc. ) and only direct children.

Ivan Debnár wrote: > The current subtasks patch displays whole subtask hierarchy the issue is part of. > This patch to jessup's patch from 161 changes _subissues_list.rhtml so that only > # ancestors of issue selected are displayed > # only direct children of selected issues are displayed > > This significantly helps if you have large ( 40+ in several levels ) number of subtasks. And also it helps to make the issue relations easier to read. > > You see who is parent ( and it's parent, etc. ) and only direct children. I imagine some people would want both behaviours (for example I have a very limited hierachy of Spring->Story/TechStory->Task trackers and it is useful for me to see *everything* against a 'Sprint' tracker some times), perhaps it would be better for it to be configurable ? As a side-note all these patches are a very poor way to manage this stuff, I was rather hoping that Eric or JP would give a clue on whether we should give up with the patch and go back to feeding back into the original plugin, or alternatively suggest we keep an uptodate git branch that we can work on rather than repeatedly applying the same patches (mainly because our rights don't let us remove the old/deprecated patches!!) -cj.

Ivan Debnár wrote: > Also fixes offering "closed" versions to user in this Add / Edit form. You will still get offered a 'closed' version when the issue already belongs to that version won't you? (At one point the shared_version stuff didn't support that) Otherwise if you need to update an issue against a closed version the version is removed from the issue on update?

I've jsut run Ciaran's patch against 1.9.2 and it stopped while looking for a file. Can someone point out the problem? <pre> | create mode 100644 public/images/contract.png | create mode 100644 public/images/corner-dots.gif | create mode 100644 public/images/expand.png | |diff --git a/app/controllers/issues_controller.rb b/app/controllers/issues_controller.rb |index d2e7b5a..0d0c3e2 100644 |--- a/app/controllers/issues_controller.rb |+++ b/app/controllers/issues_controller.rb </pre>

Scott Tearle wrote: > I've jsut run Ciaran's patch against 1.9.2 and it stopped while looking for a file. Can someone point out the problem? > > [...] No idea, I just do 'git apply <foo>.patch' at the root of the cloned repository ...

Ok I figured out the patch problem. Now I'm getting this error: uninitialized constant Query::ViewOption

ciaran jessup wrote: > I imagine some people would want both behaviours (for example I have a very limited hierachy of Spring->Story/TechStory->Task trackers and it is useful for me to see *everything* against a 'Sprint' tracker some times), perhaps it would be better for it to be configurable ? Fully agree, however I can't imagigne how to add a setting (new to redmine code and ruby in general), ideally a per project setting. > > As a side-note all these patches are a very poor way to manage this stuff, I was rather hoping that Eric or JP would give a clue on whether we should give up with the patch and go back to feeding back into the original plugin, or alternatively suggest we keep an uptodate git branch that we can work on rather than repeatedly applying the same patches (mainly because our rights don't let us remove the old/deprecated patches!!) > So I see you put it on github already thats fine with me ( you can include my patches if you want / at least the shared-versions one). However there should be some governance so that there is "official" source, and since this really is one of the most important plugins, I would like some of redmine gurus steer us. > You will still get offered a 'closed' version when the issue already belongs to that version won't you? (At one point the shared_version stuff didn't support that) Otherwise if you need to update an issue against a closed version the version is removed from the issue on update? The algorithm to fetch available versions is the same as in context-menu, so should work as expected.

I soooo want to see this as a part of version 1.0 This would create a whole new dimension to Redmine, so rather postpone the version a month or 2. Just my 5 cents *+1* (in lack of voting possibilities :-)

+1 as well! In particular I'd like to see relationships in the gantt chart somehow.

+1 here too. Especially the Gantt chart-grouping.

ciaran jessup: Thanks for picking up the ball on this, I've been overly busy this year. I'm planning to review your changes later but I wanted to post this here first. All: I've pushed up my branches to github. I'll try to merge in the changes since my patch and also upgrade it for the latest trunk. * Full raw changes (showing each change separately) - http://github.com/edavis10/redmine_branches/tree/subtasks * Rebased version of the changes, which is the patch uploaded here - http://github.com/edavis10/redmine_branches/tree/subtasks-patch I've also setup a demo site with this code and some sample data. Go to http://redmine-subtasks.heroku.com/projects/hagenes1/issues and login as the user demo/demo.

Eric Davis wrote: > ciaran jessup: > > Thanks for picking up the ball on this, I've been overly busy this year. I'm planning to review your changes later but I wanted to post this here first. > > All: > > I've pushed up my branches to github. I'll try to merge in the changes since my patch and also upgrade it for the latest trunk. > > * Full raw changes (showing each change separately) - http://github.com/edavis10/redmine_branches/tree/subtasks > * Rebased version of the changes, which is the patch uploaded here - http://github.com/edavis10/redmine_branches/tree/subtasks-patch > > I've also setup a demo site with this code and some sample data. Go to http://redmine-subtasks.heroku.com/projects/hagenes1/issues and login as the user demo/demo. Thank you for sorting this Eric, a git repo is going to be a much saner way of getting any bugs/feature discussions ironed out :) Just out of interest if one was to move their redmine installation to this branch do you think it would be feasible that at-some-point-in-the-future when (hopefully) this is accepted into the core it would be possible to switch an installation back to the 'master' without too much pain (crucially no loss of data ;) ) ?

Hey, looks not bad... and already with Ajax add functionality ;-) BTW: you have seen my post here about the idea how the adding of relationships or partent issues can look like ? http://www.redmine.org/issues/3428#note-4 Holger

Really good work, Eric! I have tested the installation on heroku and it works really great so far! I have recognized following issues: - In the subtasks list of an issue it is not easy to see the tracker of the subissues. Maybe we can include the possibilty to set an icon for the tracker (default icon for bug, feature, support). This icon could be shown than in the list and a icon tooltip which shows the name of the tracker. What do you think? - At first I have created a subissue of an existing issue and set the done to 100% of the subissue. After doing that I have seen that the parent issue was changed to 100%, too. After creating a second subissue the done status was not recalculated... Thanks, Jens

In reviewing the feature, I had the following thoughts (take them for what they are worth): - the hierarchy view in the bug is nice, but it would be equally nice in the issues view - It would be nice to be able to enter new issues in hierarchy mode (rather than create a new issue, associate a parent, etc.) and adjust the hierarchy. If it was possible to do either of these, I couldn't figure it out. By way of example, outline mode in many text editors allows one to quickly create a list of tasks, move the relationships around (both indent, outdent, as well as vertically for a task and its subtasks). Being able to then group assign blockers and estimates could also quickly complete a Gantt chart.

Steven Friedman wrote: > - the hierarchy view in the bug is nice, but it would be equally nice in the issues view But there is hierarchical view in the issue list, look at "test-parent-grouping-query" under "Custom queries" on the right side... > - It would be nice to be able to enter new issues in hierarchy mode (rather than create a new issue, associate a parent, etc.) and adjust the hierarchy. But we can, look at "Add sub-issue" in the issue menu, just below the main menu. You can add issues that are child of current issue (or sub-issue) It looks promizing by the way...

Hi, I downloaded the lateste version of the plugin, http://github.com/hron/redmine_subtasks/tree, and after installing awesome_nested_set i get "can't convert Hash into String" when running rake db:migrate_plugins. Can anyone help me? Im running 0.9.3.stable. Thanks.