Redmine

This is how far I come before it fails:

C:\RoR\redmine>rake db:migrate_plugins RAILS_ENV="production"
(in C:/RoR/redmine)
Migrating engines...
Migrating actionwebservice...
Migrating acts_as_activity_provider...
Migrating acts_as_attachable...
Migrating acts_as_customizable...
Migrating acts_as_event...
Migrating acts_as_list...
Migrating acts_as_searchable...
Migrating acts_as_tree...
Migrating acts_as_versioned...
Migrating acts_as_watchable...
Migrating classic_pagination...
Migrating coderay-0.7.6.227...
Migrating gloc-1.1.0...
Migrating gravatar...
Migrating redmine_issues_group...
1 AddQueriesGroupBy: migrating ===========================================
-- add_column(:queries, :group_by, :string)
-> 1.3120s
1 AddQueriesGroupBy: migrated (1.3120s) ==================================

(See full trace by running task with --trace)

Any ideas as to the cause?

Oh yes, forgot to mention, we use 0.8.4 of Redmine.

Lars Pehrsson wrote:

Any ideas as to the cause?

See PluginIssuesGroup. You have to install awesome_nested_set plugin.

Hi Andrew
I did install the "awesome_nested_set plugin" (same directory as the grouping plug-in)
and followed below instructions:

1.Download from http://github.com/Ubik/redmine_issues_group/ into /vendor/plugins/redmine_issues_group
2.For Redmine 0.8.x install awesome_nested_set plugin also into /vendor/plugins/ from http://github.com/collectiveidea/awesome_nested_set
3.Do in a command shell:
rake db:migrate_plugins RAILS_ENV="production"4.Restart Redmine (Apache, Mongrel, WEBrick e.t.c)

Hi Andrew. it seems that your plugin doesn't work together with my plugin. he is attached.
When I click in Issues show the error below happen.

ActionView::TemplateError (undefined method `column_header_with_spans' for #<ActionView::Base:0x56ff8d8>) on line #9 of issues/_list.rhtml:
6: </th>
7: <%= sort_header_tag('id', :caption => '#', :default_order => 'desc') >
8: < query.columns.each do |column| >
9: <= column_header_with_spans(column) >
10: < end %>
11: </tr></thead>
12: <tbody>

vendor/plugins/redmine_issues_group/app/views/issues/_list.rhtml:9:in `_run_erb_47vendor47plugins47redmine_issues_group47app47views47issues47_list46rhtml'
    vendor/plugins/redmine_issues_group/app/views/issues/_list.rhtml:8:in `each'
    vendor/plugins/redmine_issues_group/app/views/issues/_list.rhtml:8:in `_run_erb_47vendor47plugins47redmine_issues_group47app47views47issues47_list46rhtml'
    vendor/rails/actionpack/lib/action_view/helpers/capture_helper.rb:141:in `call'
    vendor/rails/actionpack/lib/action_view/helpers/capture_helper.rb:141:in `capture_erb_with_buffer'
    vendor/rails/actionpack/lib/action_view/helpers/capture_helper.rb:44:in `capture'
    vendor/rails/actionpack/lib/action_view/helpers/form_tag_helper.rb:443:in `form_tag_in_block'
    vendor/rails/actionpack/lib/action_view/helpers/form_tag_helper.rb:39:in `form_tag'
    vendor/plugins/redmine_issues_group/app/views/issues/_list.rhtml:1:in `_run_erb_47vendor47plugins47redmine_issues_group47app47views47issues47_list46rhtml'
    vendor/rails/actionpack/lib/action_view/base.rb:342:in `send'
    vendor/rails/actionpack/lib/action_view/base.rb:342:in `execute'
    vendor/rails/actionpack/lib/action_view/template_handlers/compilable.rb:29:in `send'
    vendor/rails/actionpack/lib/action_view/template_handlers/compilable.rb:29:in `render'
    vendor/rails/actionpack/lib/action_view/partial_template.rb:20:in `render'
    vendor/rails/actionpack/lib/action_controller/benchmarking.rb:30:in `benchmark'
    vendor/rails/actionpack/lib/action_view/partial_template.rb:19:in `render'
    vendor/rails/actionpack/lib/action_view/template.rb:22:in `render_template'
    vendor/rails/actionpack/lib/action_view/partials.rb:110:in `render_partial'
    vendor/rails/actionpack/lib/action_view/base.rb:277:in `render'
    app/views/issues/index.rhtml:43:in `_run_erb_47app47views47issues47index46rhtml'
    vendor/rails/actionpack/lib/action_view/base.rb:342:in `send'
    vendor/rails/actionpack/lib/action_view/base.rb:342:in `execute'
    vendor/rails/actionpack/lib/action_view/template_handlers/compilable.rb:29:in `send'
    vendor/rails/actionpack/lib/action_view/template_handlers/compilable.rb:29:in `render'
    vendor/rails/actionpack/lib/action_view/template.rb:35:in `render'

some help?

Alexey Lustin wrote:

Vitaly Klimov wrote:

I have posted temporary solution to fix duplicate journal entries in the Issue #3690 comments

did the anybody made this fix ?

may be someone create the patch - in which class and how apply this solution

Thanks in advance

Vitaliy, this temporary solution brokes ability to post issue reply via email.

Hello.
It is possible to to move subtask to another parent issue? Or make subtask as top issue (no parent)?

Roland Discein wrote:

Alexey Lustin wrote:

Vitaly Klimov wrote:

I have posted temporary solution to fix duplicate journal entries in the Issue #3690 comments

did the anybody made this fix ?

may be someone create the patch - in which class and how apply this solution

Thanks in advance

Vitaliy, this temporary solution brokes ability to post issue reply via email.

Quite possibly - i am not using email ability. This is why i called this temporary. Although i fail to see how this could broke the email ability. This is the best i can do to resolve this issue in my case - i am not author of the plugin and my knowledge of Ruby is very limited. If anyone would like to further investigate this issue with repeating callbacks - feel free to do it.

Alexey Preskenis wrote:

Hello.
It is possible to to move subtask to another parent issue? Or make subtask as top issue (no parent)?

Yes, on the issue list, right click on the subtask, select change parent.

On the Parent field, leave it blank to make it "top issue" or put the new parent issue#.

Thales Ferreira wrote:

Hi Andrew. it seems that your plugin doesn't work together with my plugin. he is attached.
When I click in Issues show the error below happen.

ActionView::TemplateError (undefined method `column_header_with_spans' for #<ActionView::Base:0x56ff8d8>) on line #9 of issues/_list.rhtml:
6: </th>
7: <%= sort_header_tag('id', :caption => '#', :default_order => 'desc') >
8: < query.columns.each do |column| >
9: <= column_header_with_spans(column) >
10: < end %>
11: </tr></thead>
12: <tbody>

I find out the error happen when I put in any /lib plugins folder call's to require 'application' and require 'issues_controller'.
Maybe error on redmine or rails plugins?

Thanks in one advance.

Updated spanish localization files.

Regards

I installed the plugin fine after carefully reading through the issues here. I'm on 0.8.4 redmine bitnami.

While the plugin appeared to work fine at first, after a while I noticed that only administrators are able to add subissues. Regular users don't seem to have the Add link appear in the Subissues heading of issues.

Any ideas why this might be the case?

Ted

Set checkbox "EditParent" in cheked state in options (permissions, "issue tracking" block). see attached image:

Hi
Thanks for this indeed useful plugin!
I have, though, some problems using it.
First of all, when querying over a large number of issues, it seems it groups just on issues on the first page: changing page it loses grouping and it is possible to find out that some issues weren't counted on the first page. Is this a problem just in my Redmine (0.8.4 & 0.8.5)?
The second problem is that I installed it with some issues already inserted on the db, so fields lft and rgt were all null for these ones. Querying them resulted in an error I resolved manually inputing all the values needed in those two fields.
Last, is it possible to have multiple grouping function as an additional feature in one of the next releases? It would add a lot to the plugin!
Best regards
LR

raldred's fork at http://github.com/raldred/redmine_issues_group provides some fixes for trunk, and minor additional functionality. It also installs without the re-branching malarkey ;)

Further to that, here's a patch against raldred's fork that allows adding a description when creating a sub-task.

diff --git a/app/controllers/issues_controller.rb b/app/controllers/issues_controller.rb
index e49bbe6..93618df 100644
--- a/app/controllers/issues_controller.rb
+++ b/app/controllers/issues_controller.rb
@@ -55,6 +55,7 @@ class IssuesController < ApplicationController
       @issues.each do |issue|
         issue.init_journal(User.current)
         issue.subject = params[:new_subject]
+        issue.description = params[:new_description]

         #unsaved_issue_ids << issue.id unless
         i2 = issue.move_to(@target_project, new_tracker, params[:copy_options])
@@ -98,4 +99,4 @@ class IssuesController < ApplicationController
     end
   end
   alias_method_chain :retrieve_query, :groupby
-end
\ No newline at end of file
+end
diff --git a/app/views/issues/_add_subissue.rhtml b/app/views/issues/_add_subissue.rhtml
index 072b3d8..8c26d25 100644
--- a/app/views/issues/_add_subissue.rhtml
+++ b/app/views/issues/_add_subissue.rhtml
@@ -19,8 +19,8 @@
         $j("#dialog").dialog({
             bgiframe: true,
             autoOpen: false,
-            width: 500,
-      height: 270,
+            width: 728,
+            height: 490,
             modal: true,
             buttons: {
                 '<%= l(:button_add) %>': function() {
@@ -82,6 +82,9 @@
 <p><label for="new_assigned_to_id"><%=l(:field_assigned_to)%>:</label>
 <%= select_tag "new_assigned_to_id", options_from_collection_for_select(@issue.assignable_users, "id", "name", @issue.assigned_to_id) %></p>

+<p><label for="new_description"><%=l(:field_description)%>:</label>
+<%= text_area_tag "new_description", @issue.description, :size => '50x6' %></p>
+
 </div>

 <% submit_tag l(:button_add) %>

Hi All

nice plugin.....I have a couple of questions/suggestions;

1). Is there any way of calculating % complete based upon the status of sub-issues, specifically with estimated hours rather than number of sub-issues complete.
2). It would be good to have a grouping feature on the 'update history' of any particular issue, so that peoples questions and responses can be viwed as threaded groups instead of a huge long list of queries - a bit like the discussion forum just embedded into a ticket.
3). Can we see relations between parent/child issues on the gantt?

Regards

Chris

Here are a few patches that I have made with version 0.1.6 of the plugin.

The patch to allow adding a description when creating subtasks is the same as the one that Peter Fern posted but should be applied to the 0.1.6 release instead of raldred's fork.

The patch to disable the ability to collapse the subtask view may not be a step forward in usability, but I like how it cleans up the view.

Please note that while I have spent some time testing these patches, you may find some issues with them.

– Brian Wells

Hello Im using Redmine 0.8.5.devel.2982 (MySQL) and istalled the pluging. So when I was checking the features as shown on http://www.redmine.org/wiki/redmine/PluginIssuesGroup the add subissue feature always show me an

Failed to create subissue

Felipe Campo wrote:

Hello Im using Redmine 0.8.5.devel.2982 (MySQL) and istalled the pluging. So when I was checking the features as shown on http://www.redmine.org/wiki/redmine/PluginIssuesGroup the add subissue feature always show me an
[...]
message, where I cant see to check what is wrong or is something required ?

I was looking in debug mdoe and fount this message:

Redirected to http://intranet:5000/issues/5783
Completed in 1202ms (DB: 88) | 302 Found [http://intranet/issues/copy_subissue]

The it can be seen a that the port thar the app is using is the 5000 and when I tru to make a subtask the app it
s looking in the 80 port. I think that is a bug but i dont know where o what i should do to fix it

Felipe Campo wrote:

Felipe Campo wrote:

Hello Im using Redmine 0.8.5.devel.2982 (MySQL) and istalled the pluging. So when I was checking the features as shown on http://www.redmine.org/wiki/redmine/PluginIssuesGroup the add subissue feature always show me an
[...]
message, where I cant see to check what is wrong or is something required ?

I was looking in debug mdoe and fount this message:

Redirected to http://intranet:5000/issues/5783
Completed in 1202ms (DB: 88) | 302 Found [http://intranet/issues/copy_subissue]

The it can be seen a that the port thar the app is using is the 5000 and when I tru to make a subtask the app it
s looking in the 80 port. I think that is a bug but i dont know where o what i should do to fix it

The port wasnt the problem i change a little bit the code and figuere out thar the save method is crashing because the priority and the required custom fields are invalid. I put the priority but the custom values stopped me the message is "issuecustom_values,is invalid"

Felipe Campo wrote:

Felipe Campo wrote:

Felipe Campo wrote:

Hello Im using Redmine 0.8.5.devel.2982 (MySQL) and istalled the pluging. So when I was checking the features as shown on http://www.redmine.org/wiki/redmine/PluginIssuesGroup the add subissue feature always show me an
[...]
message, where I cant see to check what is wrong or is something required ?

I was looking in debug mdoe and fount this message:

Redirected to http://intranet:5000/issues/5783
Completed in 1202ms (DB: 88) | 302 Found [http://intranet/issues/copy_subissue]

The it can be seen a that the port thar the app is using is the 5000 and when I tru to make a subtask the app it
s looking in the 80 port. I think that is a bug but i dont know where o what i should do to fix it

The port wasnt the problem i change a little bit the code and figuere out thar the save method is crashing because the priority and the required custom fields are invalid. I put the priority but the custom values stopped me the message is "issuecustom_values,is invalid"

So i dont know ruby and I just did it with instincts , the thing is im dont know how to patch nor ror nor redmine
so here is the result of hown I fixed it. Please someone do it in the right way
added to {plgin}/app/views/issues/_add_subissue.rhtml
tooked from /app/views/issues/{ _form_custom_fields.rhtml, _form.rhtml }
i didnt know how deal with priorities so i tooked from the parent

<div class="splitcontentleft">
<% i = 0 %>
<% split_on = (@issue.custom_field_values.size / 2.0).ceil - 1 %>
<% @issue.custom_field_values.each do |value| %>
        <p><%= custom_field_tag_with_label :issue, value %></p>
<% if i == split_on -%>
</div><div class="splitcontentright">
<% end -%>
<% i += 1 -%>
<% end -%>
</div>
<div style="clear:both;"> </div>

now the controller , the challenge i added these lines

      i2.priority = p_issue.priority

      # i2.custom_field_values = params[:custom_field_values] ? params[:custom_field_values].reject {|k,v| v.blank?} : nil
     if params[:issue].is_a?(Hash)
      i2.attributes = params[:issue]
      # @issue.watcher_user_ids = params[:issue]['watcher_user_ids'] if User.current.allowed_to?(:add_issue_watchers, @project)
    end

I'm using redmine 0.8.3 and installed redmine_issues_group.zip without problems, but when I installed redmine_issues_group_0_1_1.zip (or 0_1_2.zip ... or ... 0_1_6.zip) I can't run migrate_plugins with success because "rake aborted!".

• Invoke db:migrate_plugins (first_time)
• Invoke environment (first_time)
• Execute environment
  rake aborted!
  no such file to load -- awesome_nested_set
  /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'
  /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require'
  /data/www/redmine-0.8.3/vendor/rails/activesupport/lib/active_support/dependencies.rb:510:in `require'
  /data/www/redmine-0.8.3/vendor/rails/activesupport/lib/active_support/dependencies.rb:355:in `new_constants_in'
  /data/www/redmine-0.8.3/vendor/rails/activesupport/lib/active_support/dependencies.rb:510:in `require'
  /data/www/redmine-0.8.3/vendor/plugins/redmine_issues_group/lib/issue_relation_patch.rb:2
  /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'
  /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require'
  /data/www/redmine-0.8.3/vendor/rails/activesupport/lib/active_support/dependencies.rb:510:in `require'
  /data/www/redmine-0.8.3/vendor/rails/activesupport/lib/active_support/dependencies.rb:355:in `new_constants_in'
  /data/www/redmine-0.8.3/vendor/rails/activesupport/lib/active_support/dependencies.rb:510:in `require'
  /data/www/redmine-0.8.3/vendor/plugins/redmine_issues_group/init.rb:6:in `evaluate_init_rb'
  /var/www/redmine-0.8.3/vendor/rails/railties/lib/rails/plugin.rb:95:in `evaluate_init_rb'
  /data/www/redmine-0.8.3/vendor/rails/activesupport/lib/active_support/core_ext/kernel/reporting.rb:11:in `silence_warnings'
  /var/www/redmine-0.8.3/vendor/rails/railties/lib/rails/plugin.rb:91:in `evaluate_init_rb'
  /var/www/redmine-0.8.3/vendor/rails/railties/lib/rails/plugin.rb:44:in `load'
  /data/www/redmine-0.8.3/config/../vendor/plugins/engines/lib/engines/plugin.rb:77:in `load'
  /var/www/redmine-0.8.3/vendor/rails/railties/lib/rails/plugin/loader.rb:33:in `load_plugins'
  /var/www/redmine-0.8.3/vendor/rails/railties/lib/rails/plugin/loader.rb:32:in `each'
  /var/www/redmine-0.8.3/vendor/rails/railties/lib/rails/plugin/loader.rb:32:in `load_plugins'
  /var/www/redmine-0.8.3/vendor/rails/railties/lib/initializer.rb:292:in `load_plugins'
  /var/www/redmine-0.8.3/vendor/rails/railties/lib/initializer.rb:142:in `process'
  /var/www/redmine-0.8.3/vendor/rails/railties/lib/initializer.rb:97:in `send'
  /var/www/redmine-0.8.3/vendor/rails/railties/lib/initializer.rb:97:in `run'
  /data/www/redmine-0.8.3/config/environment.rb:20
  /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'
  /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require'
  /data/www/redmine-0.8.3/vendor/rails/activesupport/lib/active_support/dependencies.rb:510:in `require'
  /data/www/redmine-0.8.3/vendor/rails/activesupport/lib/active_support/dependencies.rb:355:in `new_constants_in'
  /data/www/redmine-0.8.3/vendor/rails/activesupport/lib/active_support/dependencies.rb:510:in `require'
  /data/www/redmine-0.8.3/vendor/rails/railties/lib/tasks/misc.rake:3
  /usr/lib/ruby/1.8/rake.rb:546:in `call'
  /usr/lib/ruby/1.8/rake.rb:546:in `execute'
  /usr/lib/ruby/1.8/rake.rb:541:in `each'
  /usr/lib/ruby/1.8/rake.rb:541:in `execute'
  /usr/lib/ruby/1.8/rake.rb:508:in `invoke_with_call_chain'
  /usr/lib/ruby/1.8/rake.rb:501:in `synchronize'
  /usr/lib/ruby/1.8/rake.rb:501:in `invoke_with_call_chain'
  /usr/lib/ruby/1.8/rake.rb:518:in `invoke_prerequisites'
  /usr/lib/ruby/1.8/rake.rb:1183:in `each'
  /usr/lib/ruby/1.8/rake.rb:1183:in `send'
  /usr/lib/ruby/1.8/rake.rb:1183:in `each'
  /usr/lib/ruby/1.8/rake.rb:515:in `invoke_prerequisites'
  /usr/lib/ruby/1.8/rake.rb:507:in `invoke_with_call_chain'
  /usr/lib/ruby/1.8/rake.rb:501:in `synchronize'
  /usr/lib/ruby/1.8/rake.rb:501:in `invoke_with_call_chain'
  /usr/lib/ruby/1.8/rake.rb:494:in `invoke'
  /usr/lib/ruby/1.8/rake.rb:1931:in `invoke_task'
  /usr/lib/ruby/1.8/rake.rb:1909:in `top_level'
  /usr/lib/ruby/1.8/rake.rb:1909:in `each'
  /usr/lib/ruby/1.8/rake.rb:1909:in `top_level'
  /usr/lib/ruby/1.8/rake.rb:1948:in `standard_exception_handling'
  /usr/lib/ruby/1.8/rake.rb:1903:in `top_level'
  /usr/lib/ruby/1.8/rake.rb:1881: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

Alberto Butrico wrote:

I'm using redmine 0.8.3 and installed redmine_issues_group.zip without problems, but when I installed redmine_issues_group_0_1_1.zip (or 0_1_2.zip ... or ... 0_1_6.zip) I can't run migrate_plugins with success because "rake aborted!".

root@va:/www/redmine-0.8.3# rake db:migrate_plugins RAILS_ENV=production --trace
(in /data/www/redmine-0.8.3)

• Invoke db:migrate_plugins (first_time)
• Invoke environment (first_time)
• Execute environment
  rake aborted!
  no such file to load -- awesome_nested_set

As the error says, and the comments tell you in this page, you need to install the 'awesome_nested_set' rails plugin.

Andrew Rudenko wrote:

Got an error when execute command:
rake db:migrate_plugins RAILS_ENV="production" > PGError: ERROR: current transaction is aborted, commands ignored until end of transaction block > : INSERT INTO schema_migrations (version) VALUES ('1-redmine_issues_group') >

Exact same thing here !
We are using the r2924 from trunk.
We also run PostgreSQL, maybe this is the source of the problem ?