Ticket grouping plugin

Added by Andrew Chaika over 15 years ago

I have developed ticket (issues) grouping plugin and tested it on current trunk.
There is a sample screenshot:

Maybe it will be usefull for someone.

redmine_issues_group.png (39.2 KB) redmine_issues_group.png
redmine_issues_group.zip (12 KB) redmine_issues_group.zip

Replies (217)

RE: Ticket grouping plugin - Added by Alberto Butrico about 15 years ago

I maked a fresh install of redmine-0.8.7 and on a new database too.
I installed without problems the issuses_group 0.1.6 plugin but when I go to "Issues" link I get this error:

Internal error
An error occurred on the page you were trying to access.
If you continue to experience problems please contact your redMine administrator for assistance.

Looking on log file I found this:

Session ID: feee2d55be6ddf821aaa04dd1075c181
Parameters: {"project_id"=>"scp2010", "action"=>"new", "controller"=>"issues"}
Rendering template within layouts/base
Rendering issues/new
Completed in 0.15290 (6 reqs/sec) | Rendering: 0.09855 (64%) | DB: 0.02095 (13%) | 200 OK [http://localhost/scp2/projects/scp2010/issues/new]

Processing IssuesController#index (for ::1 at 2009-11-22 23:45:36) [GET]
  Session ID: feee2d55be6ddf821aaa04dd1075c181
  Parameters: {"project_id"=>"scp2010", "action"=>"index", "controller"=>"issues"}
Rendering template within layouts/base
Rendering issues/index.rhtml

ActionView::TemplateError (undefined method `group_by' for #<Query:0xb6aca72c>) on line #109 of queries/_filters.rhtml:
106: <tr>
107: <td class="add-filter">
108: <%= l(:label_group_by) %>:
109: <%= select_tag 'group_by', options_for_select([["",""], [l(:label_main_project),:main_project]] + query.available_columns.collect {|column| [column.caption, column.name]}, (query.group_by && query.group_by != "" ? query.group_by.to_sym : "")), 
110:                                     :class => "select-small", 
111:                                     :style => "width: 150px" %>
112: </td>

    vendor/rails/activerecord/lib/active_record/attribute_methods.rb:256:in `method_missing'
    vendor/plugins/redmine_issues_group/app/views/queries/_filters.rhtml:109:in `_run_erb_47vendor47plugins47redmine_is:
sues_group47app47views47queries47_filters46rhtml'
    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:8:in `_run_erb_47app47views47issues47index46rhtml'
    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'
    app/views/issues/index.rhtml:5: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'
    vendor/rails/actionpack/lib/action_view/template.rb:22:in `render_template'
    vendor/rails/actionpack/lib/action_view/base.rb:248:in `render_file'
    vendor/rails/actionpack/lib/action_controller/base.rb:1112:in `render_for_file'
    vendor/rails/actionpack/lib/action_controller/base.rb:872:in `render_with_no_layout'
    vendor/rails/actionpack/lib/action_controller/layout.rb:251:in `render_without_benchmark'
    vendor/rails/actionpack/lib/action_controller/benchmarking.rb:51:in `render'
    vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:8:in `realtime'
    vendor/rails/actionpack/lib/action_controller/benchmarking.rb:51:in `render'
    app/controllers/issues_controller.rb:71:in `index'
    vendor/rails/actionpack/lib/action_controller/mime_responds.rb:131:in `call'
    vendor/rails/actionpack/lib/action_controller/mime_responds.rb:131:in `custom'
    vendor/rails/actionpack/lib/action_controller/mime_responds.rb:160:in `call'
    vendor/rails/actionpack/lib/action_controller/mime_responds.rb:160:in `respond'
    vendor/rails/actionpack/lib/action_controller/mime_responds.rb:154:in `each'
    vendor/rails/actionpack/lib/action_controller/mime_responds.rb:154:in `respond'
    vendor/rails/actionpack/lib/action_controller/mime_responds.rb:107:in `respond_to'
    app/controllers/issues_controller.rb:70:in `index'
    vendor/rails/actionpack/lib/action_controller/base.rb:1166:in `send'
    vendor/rails/actionpack/lib/action_controller/base.rb:1166:in `perform_action_without_filters'
    vendor/rails/actionpack/lib/action_controller/filters.rb:579:in `call_filters'
    vendor/rails/actionpack/lib/action_controller/filters.rb:572:in `perform_action_without_benchmark'
    vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
    /usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
    vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
    vendor/rails/actionpack/lib/action_controller/rescue.rb:201:in `perform_action_without_caching'
    vendor/rails/actionpack/lib/action_controller/caching/sql_cache.rb:13:in `perform_action'
    vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in `cache'
    vendor/rails/activerecord/lib/active_record/query_cache.rb:8:in `cache'
    vendor/rails/actionpack/lib/action_controller/caching/sql_cache.rb:12:in `perform_action'
    vendor/rails/actionpack/lib/action_controller/base.rb:529:in `send'
    vendor/rails/actionpack/lib/action_controller/base.rb:529:in `process_without_filters'
    vendor/rails/actionpack/lib/action_controller/filters.rb:568:in `process_without_session_management_support'
    vendor/rails/actionpack/lib/action_controller/session_management.rb:130:in `process'
    vendor/rails/actionpack/lib/action_controller/base.rb:389:in `process'
    vendor/rails/actionpack/lib/action_controller/dispatcher.rb:149:in `handle_request'
    vendor/rails/actionpack/lib/action_controller/dispatcher.rb:107:in `dispatch'
    vendor/rails/actionpack/lib/action_controller/dispatcher.rb:104:in `synchronize'
    vendor/rails/actionpack/lib/action_controller/dispatcher.rb:104:in `dispatch'
    vendor/rails/actionpack/lib/action_controller/dispatcher.rb:120:in `dispatch_cgi'
    vendor/rails/actionpack/lib/action_controller/dispatcher.rb:35:in `dispatch'
    vendor/rails/railties/lib/fcgi_handler.rb:103:in `process_request'
    vendor/rails/railties/lib/fcgi_handler.rb:153:in `with_signal_handler'
    vendor/rails/railties/lib/fcgi_handler.rb:101:in `process_request'
    vendor/rails/railties/lib/fcgi_handler.rb:78:in `process_each_request'
    /var/lib/gems/1.8/gems/fcgi-0.8.8/lib/fcgi.rb:612:in `each_cgi'
    /var/lib/gems/1.8/gems/fcgi-0.8.8/lib/fcgi.rb:609:in `each'
    /var/lib/gems/1.8/gems/fcgi-0.8.8/lib/fcgi.rb:609:in `each_cgi'
    vendor/rails/railties/lib/fcgi_handler.rb:77:in `process_each_request'
    vendor/rails/railties/lib/fcgi_handler.rb:76:in `catch'
    vendor/rails/railties/lib/fcgi_handler.rb:76:in `process_each_request'
    vendor/rails/railties/lib/fcgi_handler.rb:50:in `process!'
    vendor/rails/railties/lib/fcgi_handler.rb:24:in `process!'
    /var/www/scp2/dispatch.fcgi:24

Rendering /data/redmine-0.8.7/public/500.html (500 Internal Server Error)

RE: Ticket grouping plugin - Added by Alberto Butrico about 15 years ago

I was wrong.
I was running "rake db:migrate" rather than "rake db:migrate_plugins"

...but now I have a new problem and it's than the "migrate_plugins" hang-up and never end.

rake db:migrate_plugins
(in /data/redmine-0.8.7)
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 collectiveidea-awesome_nested_set-222d49a...
Migrating gloc-1.1.0...
Migrating gravatar...
Migrating redmine_issues_group...

RE: Ticket grouping plugin - Added by Orcun Gok about 15 years ago

Alberto Butrico wrote:

I was wrong.
I was running "rake db:migrate" rather than "rake db:migrate_plugins"

...but now I have a new problem and it's than the "migrate_plugins" hang-up and never end.

[...]

Same problem.
I'm using redmine 0.8.6 and I've installed awesome_nested_set plugin. db:migrate_plugins stucks at "redmine_issues_group".

RE: Ticket grouping plugin - Added by Orcun Gok about 15 years ago

In myphpadmin when I look at the active mysql processes redmine process state is sleep.

Mysql process list:

  ID User Host Database Command Time Status SQL query 
Kill 31 root localhost:59732 redmine Sleep 8 --- --- 
Kill 34 root localhost:59739 mysql   Query 0 --- SHOW PROCESSLIST

Stack trace after ctrl + c :

D:\Applications\Ruby\redmine>rake db:migrate_plugins RAILS_ENV=production --trace
(in D:/Applications/Ruby/redmine)
** Invoke db:migrate_plugins (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute db:migrate_plugins
Migrating engines...
Migrating Graphs...
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 awesome_nested_set...
Migrating classic_pagination...
Migrating coderay-0.7.6.227...
Migrating gloc-1.1.0...
Migrating gravatar...
Migrating redmine_importer...
Migrating redmine_issues_group...
rake aborted!

D:/Applications/Ruby/redmine/vendor/plugins/engines/lib/engines/plugin/migrator.rb:61:in `<=>'
D:/Applications/Ruby/redmine/vendor/plugins/engines/lib/engines/plugin/migrator.rb:61:in `each'
D:/Applications/Ruby/redmine/vendor/plugins/engines/lib/engines/plugin/migrator.rb:61:in `to_a'
D:/Applications/Ruby/redmine/vendor/plugins/engines/lib/engines/plugin/migrator.rb:61:in `migrated'
D:/Applications/Ruby/redmine/vendor/rails/activerecord/lib/active_record/migration.rb:414:in `current_version'
D:/Applications/Ruby/redmine/vendor/rails/activerecord/lib/active_record/migration.rb:431:in `migrate'
D:/Applications/Ruby/redmine/vendor/rails/activesupport/lib/active_support/dependencies.rb:503:in `detect'
D:/Applications/Ruby/redmine/vendor/rails/activerecord/lib/active_record/migration.rb:431:in `each'
D:/Applications/Ruby/redmine/vendor/rails/activerecord/lib/active_record/migration.rb:431:in `detect'
D:/Applications/Ruby/redmine/vendor/rails/activerecord/lib/active_record/migration.rb:431:in `migrate'
D:/Applications/Ruby/redmine/vendor/rails/activerecord/lib/active_record/migration.rb:373:in `up'
D:/Applications/Ruby/redmine/vendor/rails/activerecord/lib/active_record/migration.rb:356:in `migrate'
D:/Applications/Ruby/redmine/vendor/plugins/engines/lib/engines/plugin/migrator.rb:23:in `migrate_plugin'
D:/Applications/Ruby/redmine/config/../vendor/plugins/engines/lib/engines/plugin.rb:122:in `migrate'
D:/Applications/Ruby/redmine/lib/tasks/migrate_plugins.rake:8
D:/Applications/Ruby/redmine/lib/tasks/migrate_plugins.rake:5:in `each'
D:/Applications/Ruby/redmine/lib/tasks/migrate_plugins.rake:5
D:/Applications/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call'
D:/Applications/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute'
D:/Applications/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each'
D:/Applications/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute'
D:/Applications/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain'
D:/Applications/Ruby/lib/ruby/1.8/monitor.rb:242:in `synchronize'
D:/Applications/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
D:/Applications/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke'
D:/Applications/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task'
D:/Applications/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level'
D:/Applications/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each'
D:/Applications/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level'
D:/Applications/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'
D:/Applications/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level'
D:/Applications/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run'
D:/Applications/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'
D:/Applications/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
D:/Applications/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31
D:/Applications/Ruby/bin/rake:19:in `load'

RE: Ticket grouping plugin - Added by liny lin almost 15 years ago

Kael Estermann wrote:

Alexey Lustin wrote:

[...]

Andrew your forgot that in trunk Redmine changes the API - user now can have collection of roles

for example
http://www.redmine.org/issues/3347

I have the plugin installed on Redmine 0.8.4 and Plugin is 0.1.4. if i try to add a subissues the an internal error is occurs:

Processing IssuesController#copy_subissue (for 192.168.1.61 at 2009-05-30 20:17:07) [POST]
Session ID: 99c25acfa921e28c5a9066a6124865db
Parameters: {"new_project_id"=>"1", "new_tracker_id"=>"1", "ids"=>["1"], "new_subject"=>"Testen Icon und Bildschirm varinaten", "a
ction"=>"copy_subissue", "controller"=>"issues", "copy_options"=>{"copy"=>"1"}}

ArgumentError (wrong number of arguments (3 for 2)):
/vendor/plugins/redmine_issues_group/app/controllers/issues_controller.rb:59:in `move_to'
/vendor/plugins/redmine_issues_group/app/controllers/issues_controller.rb:59:in `copy_subissue'

Hi, does anyone know how to solve [ArgumentError (wrong number of arguments (3 for 2))] problem?
I installed redmine 0.8.7 and awesome_nested_set latest version(2009/11/27)

RE: Ticket grouping plugin - Added by Orcun Gok almost 15 years ago

This plug-in must be integrated into core/distribution and supported better...

RE: Ticket grouping plugin - Added by Mischa The Evil almost 15 years ago

Orcun Gok wrote:

This plug-in must be integrated into core/distribution (...)

Currently I would vote against for integration of this specific plugin. I'll share my ideas behind my vote;

The initial plugin's feature-set (issue-grouping) is implemented in the bleeding-edge of the Redmine core (source:/trunk) already (see issue #2679). Two other, new features were added to the plugin after that issue has been closed:

Custom-Query grouping
Subtasking

Regarding the first I'd propose that you open a new, specific issue (feature) since it hasn't been requested clearly and seperate before. Though it has been discussed roughly in the comments of issue #2679...

About the second feature: a dedicated issue exists already (see #443). It's a highly-requested feature as visible, but in my humble opinion the implementation of it seems to affect a lot of Redmine's initial design which could make it a showstopper at forehand, resulting in a decision to close the issue with the resolution "Won't fix".
As an alternative some other (plugin-)implementations were developed over time by some other third-party developers which might solve the specific needs regarding the subtasking-feature for the time being.

Orcun Gok wrote:

(...) and supported better...

I think I see your point here. But as far as I am aware of (see RE: Ticket grouping plugin) Andrew Chaika did not had the specific goal to also maintain the plugin for the long(er) term. On the other hand, he has done some updates of the plugin (see above :) so it could be that has already planned an update for the plugin already... I don't know to be honest.

/me whispers: "Keep it mind that it is all FLOSS thus support can never be "enforced" from the author. The same goes for any updates of the work. The author does not have the "obligation" to further develop nor maintain the (initial) work."

Kind regards,

Mischa.

Disclaimer: This is a reflection of my personal opinion. I am not a member of the Redmine Core Team nor I am a (highly-skilled) (Redmine core) developer either... :wink:

RE: Ticket grouping plugin - Added by m p almost 15 years ago

Martial SERON wrote:

I have this error when I select a parent issue.
[...]

got the same exact error in 0.8.7, How was this resolved?

ActionView::TemplateError (undefined method `sort_criteria' for #<Query:0xb6145468>) on line #33 of issues/_subissues_list.rhtml:

30: query.project = Herve Harster

31: query.column_names = [:id, :subject, :status, :start_date, :due_date]

32:

33: sort_init(query.sort_criteria.empty? ? 'id', 'desc' : query.sort_criteria)

34: sort_update({'id' => "#{Issue.table_name}.id"}.merge(query.available_columns.inject({}) {|h, c| h[c.name.to_s] = c.sortable; h}))

35: %>

36: <%= render :partial => 'issues/list', :locals => {:issues => @issue.children, :query => query, :group_num => 0, :level => 1, :graph => [] } %>

vendor/rails/activerecord/lib/active_record/attribute_methods.rb:256:in `method_missing'

RE: Ticket grouping plugin - Added by m p almost 15 years ago

Andrew Chaika wrote:

Current (github) version is not compatible with 0.8.x Redmine.
I have new version 0.1.6 that I use with 0.8.4 Redmine, described error in which (and some more) have fixed.
But I have not test it on trunk Redmine.

Thank you for this,

works very well with 0.8.7

happy holidays

RE: Ticket grouping plugin - Added by m p almost 15 years ago

Christopher Monk wrote:

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

just as an addition to this,

If the % Done for a subtask changes shouldn't the % Done for the parent change as well?

RE: Ticket grouping plugin - Added by Peter Fern almost 15 years ago

m p wrote:

just as an addition to this,

If the % Done for a subtask changes shouldn't the % Done for the parent change as well?

Not yet implemented - there's a whole swathe of work to be done for parent tasks to reflect updates to children. I'm working on a fork that automatically adds issue relationships between parents and children, and this is on my list of things to investigate.

RE: Ticket grouping plugin - Added by Roland Discein almost 15 years ago

People, please help us to make 0.1.6 plugin usable under redmine trunk (r3220+). When trying to edit any issue (or add one)

SystemStackError (stack level too deep):
  app/models/issue.rb:146:in `tracker_id='
  app/models/issue.rb:158:in `attributes_without_tracker_first='
  app/models/issue.rb:160:in `attributes_without_tracker_first='
  app/models/issue.rb:160:in `attributes='
  app/controllers/issues_controller.rb:183:in `edit'

Rendering /opt/redmine/public/500.html (500 Internal Server Error)

Please see help forum board here for details

RE: Ticket grouping plugin - Added by Andrew Chaika almost 15 years ago

I have catch this error. I think it's Rails upgrade related.
New version 0.1.7.

redmine_issues_group_0_1_7.zip (143 KB) redmine_issues_group_0_1_7.zip

RE: Ticket grouping plugin - Added by Robert Sanders almost 15 years ago

Very nice plugin - I wish it could be integrated with the core, as that's where it would seem to belong, but that's not your fault.

I just grabbed the latest ZIP, and it is working, or at least not causing errors; one usability issue that I just found.

Set default page size to 25 (or smaller for easier testing).
Add a couple top-level issues.
Take the last issue in the list and add a bunch of child issues (say 24 in my case).
Click on the "Issues" tab.

The result is that the listing on the first page of results shows the first couple of top-level issues, then a bunch of the child issues - BUT they are not indented. If you navigate to the second page, then suddenly you get the parent issue, and all the children are listed, this time correctly indented.

Setting the page size to 50 "fixes" this issue.

As this is a plugin and not core, I can see that this might be a little tricky to work around this problem, but for me it was confusing enough that I thought I'd post a message.

RE: Ticket grouping plugin - Added by Ez Dakit almost 15 years ago

As told Felipe Campo a month ago, priority is a non empty field in the issues table, so it fails to insert a new record into the database if this field is not defined.

I'm newby but I can`t understand how subtasking works for you fortunate people without adding this line into the issues_controller.rb file:

i2.priority = p_issue.priority

Sure missing something, but how?

RE: Ticket grouping plugin - Added by Samu Tuomisto almost 15 years ago

Andrew Chaika wrote:

I have catch this error. I think it's Rails upgrade related.
New version 0.1.7.

Should this version be compatible with Redmine 0.9?

When listing issues in any project my browser displays "HTTP 500 - Internal Server Error
The server responded with an error page.".

Redmine 0.9.0.stable.3280 (MySQL)
Mongrel_rails Version 1.1.5 (Mongrel seems to print less informative log-information compared to Webrick)
MySQL server version: 4.1.22
Rails 2.3.5
ruby 1.8.7 (2009-06-12 patchlevel 174) [i686-linux]

RE: Ticket grouping plugin - Added by Roland Discein almost 15 years ago

Samu Tuomisto wrote:

Should this version be compatible with Redmine 0.9?

Yep. u just do not know how to cook it. catch this one redmine_issues_group_0_1_7_patched.tar.gz and try.

When listing issues in any project my browser displays "HTTP 500 - Internal Server Error
The server responded with an error page.".

Have u read this ?

where is

* the error stack trace that you should find in the log file . . .

Redmine 0.9.0.stable.3280 (MySQL)
Mongrel_rails Version 1.1.5 (Mongrel seems to print less informative log-information compared to Webrick)
MySQL server version: 4.1.22
Rails 2.3.5
ruby 1.8.7 (2009-06-12 patchlevel 174) [i686-linux]

I've tested attached plugin with this environment. It works.

redmine_issues_group_0_1_7_patched.tar.gz (106 KB) redmine_issues_group_0_1_7_patched.tar.gz

RE: Ticket grouping plugin - Added by Samu Tuomisto almost 15 years ago

Thank you for answer and advices!

However your patched version doesn't work for me either. Getting following error in log.

Processing IssuesController#index (for xxx.xxx.xxx.xxx at 2010-01-12 19:22:03) [GET]
Parameters: {"project_id"=>"procdev-hr", "action"=>"index", "controller"=>"issues"}
Rendering template within layouts/base
Rendering issues/index.rhtml

ActionView::TemplateError (undefined method `column_header_with_spans' for #<ActionView::Base:0xb6faceac>) on line #9 of vendor/plugins/redmine_issues_group/app/views/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_rhtml_vendor47plugins47redmine_issues_group47app47views47issues47_list46rhtml_locals_issues_list_object_query'
    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_rhtml_vendor47plugins47redmine_issues_group47app47views47issues47_list46rhtml_locals_issues_list_object_query'
    vendor/plugins/redmine_issues_group/app/views/issues/_list.rhtml:1:in `_run_rhtml_vendor47plugins47redmine_issues_group47app47views47issues47_list46rhtml_locals_issues_list_object_query'
    app/views/issues/index.rhtml:62:in `_run_rhtml_app47views47issues47index46rhtml'
    app/controllers/issues_controller.rb:76:in `index'
    app/controllers/issues_controller.rb:75:in `index'

Rendering /var/www/html/redmine/public/500.html (500 Internal Server Error)

RE: Ticket grouping plugin - Added by Roland Discein almost 15 years ago

Can u install version 0.1.6 from this page first, then do cd where redmine root is(RAILS_ROOT), do RAILS_ENV=production rake db:migrate:upgrade_plugin_migrations; RAILS_ENV=production rake db:migrate_plugins (instructions from here then install 0.1.7_patched, restart rails and try. Also post here output of

ruby script/about

And which environment do u use when starting rails?

RE: Ticket grouping plugin - Added by Marco Gutsche almost 15 years ago

Hello,

I get this error message in log running on redmine 0.8.7:

ActionView::TemplateError (undefined method `group_by' for #<Query:0x7f5f4b51d6f8>) on line #112 of queries/_filters.rhtml:
109: <tr>
110: <td class="add-filter">
111: <%= l(:label_group_by) %>:
112: <%= select_tag 'group_by', options_for_select([["",""], [l(:label_main_project),:main_project]] + query.available_columns.collect {|column| [column.caption, column.name]}, (query.group_by && query.group_by != "" ? query.group_by.to_sym : "")),
113:                                     :class => "select-small",
114:                                     :style => "width: 150px" %>
115: </td>

The solve in this thread earlier doesn't help :(

Has someone an advice?
Thank a lot.

RE: Ticket grouping plugin - Added by Roland Discein almost 15 years ago

Please provide your environment, including rails version and redmine revision.

RE: Ticket grouping plugin - Added by Michael Jahn almost 15 years ago

I hope that's not the wrong place for that but I want to provide the german translation for the issue grouping plugin.

BTW: I use Redmine 0.9.1 with the issue grouping plugin 0.1.7_patched without errors at the moment.

de.yml (485 Bytes) de.yml

German translation

RE: Ticket grouping plugin - Added by Gennadii Omelchenko almost 15 years ago

I've got error during saving query.

Environment:

Redmine: 0.9.1
Ruby: 1.8.6
Rails: 2.3.5
Mysql: 5.
Ticket grouping plugin: 0.1.7 (patched)

Error log:

Processing QueriesController#new (for 192.168.134.16 at 2010-02-11 11:40:10) [POST]
  Parameters: {"group_by"=>"", "project_id"=>"rulesredmine", "action"=>"new", "authenticity_token"=>"QZPdfOsCqf3VAj5wmiWx7HxYnqCp9uUiYq1/RHphS4k=",
"fields"=>["status_id"], "operators"=>{"start_date"=>"<t+", "watcher_id"=>"=", "estimated_hours"=>"=", "created_on"=>">t-", "priority_id"=>"=", "cf_6"=>"=", "cf_7"=>"=", "done_ratio"=>"=", "updated_on"=>">t-", "subject"=>"~", "assigned_to_id"=>"=", "cf_8"=>"=", "tracker_id"=>"=", "cf_9"=>"=", "due_date"=>"<t+", "author_id"=>"=", "status_id"=>"o", "cf_10"=>"="}, "values"=>{"start_date"=>[""], "watcher_id"=>["me"], "estimated_hours"=>[""], "created_on"=>[""], "priority_id"=>["3"], "cf_6"=>[""], "cf_7"=>[""], "done_ratio"=>[""], "updated_on"=>[""], "subject"=>[""], "assigned_to_id"=>["me"], "cf_8"=>["Днепропетровск"], "tracker_id"=>["4"], "cf_9"=>[""], "due_date"=>[""], "author_id"=>["me"], "status_id"=>["1"], "cf_10"=>[""]}, "controller"=>"queries", "query"=>{"column_names"=>["project",
"tracker", "status", "priority", "subject", "assigned_to", "updated_on", "category", "fixed_version", "done_ratio"]}}

NameError (undefined local variable or method `current_role' for
#<QueriesController:0xf4ec4614>):
  vendor/plugins/redmine_issues_group/app/controllers/queries_controller.rb:17:in
`new'

RE: Ticket grouping plugin - Added by Andrew Chaika almost 15 years ago

Change 17th line of vendor/plugins/redmine_issues_group/app/controllers/queries_controller.rb:

@query.is_public = false unless (@query.project && current_role.allowed_to?(:manage_public_queries)) || User.current.admin?

@query.is_public = false unless User.current.allowed_to?(:manage_public_queries, @project) || User.current.admin?

RE: Ticket grouping plugin - Added by Gennadii Omelchenko almost 15 years ago

Andrew Ness Chaika

Thanks a lot!

Besides that, they must patch file vendor/plugins/redmine_issues_group/app/views/queries/_form.rhtml

line 15

<% if User.current.admin? || (@project && current_role.allowed_to?
(:manage_public_queries)) %>

change to

<% if User.current.admin? || (User.current.allowed_to?(:manage_public_queries,
@project)) %>

(151-175/217)

Project

General

Profile

Redmine