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.
Replies (217)
RE: Ticket grouping plugin - Added by Dmitry Salashnik over 15 years ago
I found small bug with text positions with russian localisation on ticket editing form:
without plugin all ok:
with plugin some texts is broken:
without_plugin.jpg (53.5 KB) without_plugin.jpg | |||
with_plugin.jpg (54.9 KB) with_plugin.jpg |
RE: Ticket grouping plugin - Added by Dmitry Salashnik over 15 years ago
Dmitry Salashnik wrote:
I found small bug with text positions with russian localisation on ticket editing form:
i use r2819
RE: Ticket grouping plugin - Added by Mykhaylo Sorochan over 15 years ago
The code in app/views/issues/_add_subissue.rhtml for 'Add subissue':
.tabular label { width: 75px; margin-left: -80px; } .tabular p { padding-left: 75px; }
overrides the application.css style.
I guess Andrew will fix that soon. For now you can just delete these lines and wait for official fix.
RE: Ticket grouping plugin - Added by Dmitry Salashnik over 15 years ago
Mykhaylo Sorochan wrote:
I guess Andrew will fix that soon.
i too :)
For now you can just delete these lines and wait for official fix.
then i have broken 'add subissue' form :(
but i found new 'feathure':
!bad lines.jpg!
bad_lines.jpg (34.4 KB) bad_lines.jpg |
RE: Ticket grouping plugin - Added by Vitaly Klimov over 15 years ago
Patrick Fratczak wrote:
Markus Knittig wrote:
Erik Dannenberg wrote:
steps to reproduce: update the status or percentage of a ticket.
the status changes in the tickethistory are displayed twice for each status change.
Have the same issue here. Have tried both 1.8.6 and 1.8.7 packages (with Rails 2.2.2) with no luck. All the status changes displayed twice on the issue view screen. Haven't tried clean install yet. Email notifications are pretty normal though - no dups there.
RE: Ticket grouping plugin - Added by Vitaly Klimov over 15 years ago
I have posted temporary solution to fix duplicate journal entries in the Issue #3690 comments
RE: Ticket grouping plugin - Added by Alexey Lustin over 15 years ago
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
RE: Ticket grouping plugin - Added by Alexey Lustin over 15 years ago
the patch look like this
svn diff app/models Index: app/models/issue.rb =================================================================== --- app/models/issue.rb (revision 2858) +++ app/models/issue.rb (working copy) @@ -56,7 +56,7 @@ named_scope :open, :conditions => ["#{IssueStatus.table_name}.is_closed = ?", false], :include => :status - after_save :create_journal + #after_save :create_journal # Returns true if usr or current user is allowed to view the issue def visible?(usr=nil) @@ -156,6 +156,12 @@ end end + def save(*args) + value = super(*args) + create_journal + return value + end + def after_save # Reload is needed in order to get the right status reload
RE: Ticket grouping plugin - Added by Maxim Chaplygin about 15 years ago
Hi. Can I install this plugin on Redmine 0.8.4.stable.2854 (MySQL). Or only on trunk version?
What is dependencies of this plugin. It would be great if you can write install manual after all these changes.
Work with clone project or duplicate issue - Added by Marcel Evenson about 15 years ago
Is there a way to have this plug in use hooks ?? That way if you duplicated an issue or cloned a project that had sub tasks that it would keep the hierarchy. Currently if you copy a project or duplicate an issue that has sub-issues the new issues will be flattened ..
RE: Ticket grouping plugin - Added by Victor Kyarginsky about 15 years ago
Hi!
I installed this plug-in (redmine_issues_group_0_1_5) into redmine v0.8.5.
Then I get a error when I try to use it.
The steps are following:
1. On task page I see unnamed label "label_subissues"
see attached file subissues1.jpg
2. When I press button "Add" I get new window
see attached file subissues2.jpg
3. When I press button "Add" I get a error
see attached file subissues3.jpg
LOG-file is
Processing IssuesController#show (for 10.0.8.152 at 2009-09-16 16:25:37) [GET] Session ID: 9a3217cc4ed719af6ac2916e188d5a97 Parameters: {"action"=>"show", "id"=>"106", "controller"=>"issues"} Rendering template within layouts/base Rendering issues/show.rhtml Completed in 0.29700 (3 reqs/sec) | Rendering: 0.23500 (79%) | DB: 0.03100 (10%) | 200 OK [http://portal.aitec.ic.rosbank.ru/issues/show/106] Processing IssuesController#copy_subissue (for 10.0.8.152 at 2009-09-16 16:26:24) [POST] Session ID: 9a3217cc4ed719af6ac2916e188d5a97 Parameters: {"new_project_id"=>"2", "new_tracker_id"=>"5", "ids"=>["106"], "new_subject"=>"Test2", "action"=>"copy_subissue", "controller"=>"issues", "copy_options"=>{"copy"=>"1"}} ActiveRecord::ActiveRecordError (You cannot move a new node): /vendor/plugins/awesome_nested_set/lib/awesome_nested_set.rb:506:in `move_to_in_set' /vendor/plugins/redmine_issues_group/lib/awesome_nested_set_issues_patch.rb:23:in `move_to_child_of' /vendor/plugins/redmine_issues_group/app/controllers/issues_controller.rb:65:in `copy_subissue' /vendor/plugins/redmine_issues_group/app/controllers/issues_controller.rb:55:in `each' /vendor/plugins/redmine_issues_group/app/controllers/issues_controller.rb:55:in `copy_subissue' /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' c:/Ruby/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/webrick_server.rb:112:in `handle_dispatch' /vendor/rails/railties/lib/webrick_server.rb:78:in `service' c:/Ruby/lib/ruby/1.8/webrick/httpserver.rb:104:in `service' c:/Ruby/lib/ruby/1.8/webrick/httpserver.rb:65:in `run' c:/Ruby/lib/ruby/1.8/webrick/server.rb:173:in `start_thread' c:/Ruby/lib/ruby/1.8/webrick/server.rb:162:in `start' c:/Ruby/lib/ruby/1.8/webrick/server.rb:162:in `start_thread' c:/Ruby/lib/ruby/1.8/webrick/server.rb:95:in `start' c:/Ruby/lib/ruby/1.8/webrick/server.rb:92:in `each' c:/Ruby/lib/ruby/1.8/webrick/server.rb:92:in `start' c:/Ruby/lib/ruby/1.8/webrick/server.rb:23:in `start' c:/Ruby/lib/ruby/1.8/webrick/server.rb:82:in `start' /vendor/rails/railties/lib/webrick_server.rb:62:in `dispatch' /vendor/rails/railties/lib/commands/servers/webrick.rb:66 c:/Ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' c:/Ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' /vendor/rails/activesupport/lib/active_support/dependencies.rb:510:in `require' /vendor/rails/activesupport/lib/active_support/dependencies.rb:355:in `new_constants_in' /vendor/rails/activesupport/lib/active_support/dependencies.rb:510:in `require' /vendor/rails/railties/lib/commands/server.rb:39 c:/Ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' c:/Ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' /script/server:3 Rendering c:/www/redmine/public/500.html (500 Internal Server Error)
Could you help me with subject?
subissues1.jpg (38.3 KB) subissues1.jpg | |||
subissues2.jpg (16.8 KB) subissues2.jpg | |||
subissues3.jpg (9.99 KB) subissues3.jpg |
RE: Ticket grouping plugin - Added by Martin G about 15 years ago
Hi,
i have some problems with the installation of the plugin.
I got the newest version(zip-file) here: http://github.com/Ubik/redmine_issues_group
Then i copied all the files into .../vendor/plugins and restarted redmine. Now i see two processes in the task manager of the pc and they are using 100% of the cpu and i cannot work anymore with redmine(proxy error 502).
What i do wrong?
RE: Ticket grouping plugin - Added by Andrew Chaika about 15 years ago
You need to do a databse migration
rake db:migrate_plugins
To see what is going on with your Redmine on error see log/production.log file.
RE: Ticket grouping plugin - Added by Martin G about 15 years ago
Sorry, but i am a newbie to ruby...
Where i have to execute this syntax?
Thanks for you patience...
RE: Ticket grouping plugin - Added by Mykhaylo Sorochan about 15 years ago
Andrew,
The bug from Виктор Кяргинский is replicable when you create the first subissue with "Tracker: (no changes)". If one will choose some tracker it works ok then. Even if after (no changes) is selected.
RE: Ticket grouping plugin - Added by Andrew Chaika about 15 years ago
Martin G, Maxim Chaplygin,
See PluginIssuesGroup.
RE: Ticket grouping plugin - Added by Martial SERON about 15 years ago
I have this error when I select a parent issue.
Processing IssuesController#show (for 10.54.73.129 at 2009-09-22 11:14:52) [GET] Session ID: f3368bb7d72658f54fe62ccc1fd45c92 Parameters: {"action"=>"show", "id"=>"204", "controller"=>"issues"} Rendering template within layouts/base Rendering issues/show.rhtml ActionView::TemplateError (undefined method `sort_criteria' for #<Query:0xb6d4cc0c>) on line #33 of issues/_subissues_list.rhtml: 30: query.project = @project 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 => [] } %> ... Rendering /srv/redmine/public/500.html (500 Internal Server Error)
RE: Ticket grouping plugin - Added by Andrew Chaika about 15 years ago
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.
RE: Ticket grouping plugin - Added by Hans Kazan about 15 years ago
With the versions 0_1_5 and 6 I get an error.
This is a clean test database freshly built from 0.8.5 and with 1 project and 2 issues.
The error is raised after adding a sub issue:
[pre]
howing issues/_subissues_list.rhtml where line #30 raised:
Project(#-626641838) expected, got Project(#-627958888)
Extracted source (around line #30):
27: <div id="subissues">
28: <%
29: query = Query.new(:name => "_")
30: query.project = Herve Harster
31: query.column_names = [:id, :subject, :status, :start_date, :due_date]
32:
33: if (query.respond_to? :sort_criteria)
Trace of template inclusion: /app/views/issues/show.rhtml
[/pre]
RE: Ticket grouping plugin - Added by Martial SERON about 15 years ago
Thanks for the 0.1.6 version.
I use redmine 0.8.4 and when I submit the new issue form... :
Processing IssuesController#new (for 10.54.73.129 at 2009-09-22 15:27:43) [POST] Session ID: f3368bb7d72658f54fe62ccc1fd45c92 Parameters: {"project_id"=>"test", "commit"=>"Créer", "action"=>"new", "controller"=>"issues", "issue"=>{"start_date"=>"", "estimated_hours"=>"", "priority_id"=>"4", "subject"=>"test de groupement", "description"=>"test", "tracker_id"=>"2", "fixed_version_id"=>"20", "category_id"=>"", "done_ratio"=>"0", "due_date"=>"", "assigned_to_id"=>"4", "status_id"=>"1"}, "attachments"=>{"1"=>{"description"=>"", "file"=>""}}} Redirected to http://10.54.73.132:3000/issues/show/208 Completed in 0.69179 (1 reqs/sec) | DB: 0.20535 (29%) | 302 Found [http://10.54.73.132/projects/test/issues/new] Processing IssuesController#show (for 10.54.73.129 at 2009-09-22 15:27:44) [GET] Session ID: f3368bb7d72658f54fe62ccc1fd45c92 Parameters: {"action"=>"show", "id"=>"208", "controller"=>"issues"} Rendering template within layouts/base Rendering issues/show.rhtml ActionView::TemplateError (Missing template issues/_subissues_list.html.erb in view path /srv/redmine/vendor/plugins/redmine_issues_group/app/views:/srv/redmine/vendor/plugins/ezfaq_plugin/app/views:/srv/redmine/app/views) on line #72 of issues/show.rhtml: 69: 70: <%= link_to_attachments @issue %> 71: 72: <%= call_hook(:view_issues_show_description_bottom, :issue => @issue) %> 73: 74: <% if authorize_for('issue_relations', 'new') || @issue.relations.any? %> 75: <hr />
RE: Ticket grouping plugin - Added by Marcel Evenson about 15 years ago
Andrew is it possible to make this plugin work with the project copy feature (from trunk) ? Currently any project that you copy gets flattened if it has sub-issues.
RE: Ticket grouping plugin - Added by Felipe Matos Moreira about 15 years ago
Hi Andrew,
I got an error while trying to create a sub-issue. I'm using Bitnami version of redmine (0.8.5) and plugin 0.1.6
It seems that the problem is on line 62 of issue_controller.rb:
i2.start_date = Time.now
issue.rb, line 117:
def validate
if self.due_date.nil? && @attributes['due_date'] && !@attributes['due_date'].empty?
errors.add :due_date, :activerecord_error_not_a_date
end
this is the line getting the error:
if self.due_date and self.start_date and self.due_date < self.start_date
errors.add :due_date, :activerecord_error_greater_than_start_date
end
if start_date && soonest_start && start_date < soonest_start
errors.add :start_date, :activerecord_error_invalid
end
end
When redmine do the validation of the sub-issue created, it gets the error:
Processing IssuesController#copy_subissue (for 10.1.164.167 at 2009-09-23 12:07:47) [POST]
Session ID: 3ca6e8ef5d0482bae3259eb3de16d48d
Parameters: {"new_subject"=>"asdasd", "new_tracker_id"=>"", "ids"=>["136"], "new_project_id"=>"11", "action"=>"copy_subissue", "new_assigned_to_id"=>"4", "controller"=>"issues", "copy_options"=>{"copy"=>"1"}}
ArgumentError (comparison of Date with Time failed):
/app/models/issue.rb:117:in `<'
/app/models/issue.rb:117:in `validate'
/vendor/rails/activerecord/lib/active_record/validations.rb:940:in `valid_without_callbacks?'
/vendor/rails/activerecord/lib/active_record/callbacks.rb:267:in `valid?'
/vendor/rails/activerecord/lib/active_record/validations.rb:910:in `save_without_dirty'
/vendor/rails/activerecord/lib/active_record/dirty.rb:75:in `save_without_transactions'
/vendor/rails/activerecord/lib/active_record/transactions.rb:106:in `save'
/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:66:in `transaction'
/vendor/rails/activerecord/lib/active_record/transactions.rb:79:in `transaction'
/vendor/rails/activerecord/lib/active_record/transactions.rb:98:in `transaction'
/vendor/rails/activerecord/lib/active_record/transactions.rb:106:in `save'
/vendor/rails/activerecord/lib/active_record/transactions.rb:118:in `rollback_active_record_state!'
/vendor/rails/activerecord/lib/active_record/transactions.rb:106:in `save'
/vendor/plugins/redmine_issues_group/app/controllers/issues_controller.rb:70:in `copy_subissue'
/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'
C:/Bitnami/RubyStack/ruby/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'
C:/Bitnami/RubyStack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:76:in `process'
C:/Bitnami/RubyStack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in `synchronize'
C:/Bitnami/RubyStack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in `process'
C:/Bitnami/RubyStack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel.rb:159:in `process_client'
C:/Bitnami/RubyStack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel.rb:158:in `each'
C:/Bitnami/RubyStack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel.rb:158:in `process_client'
C:/Bitnami/RubyStack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel.rb:285:in `run'
C:/Bitnami/RubyStack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel.rb:285:in `initialize'
C:/Bitnami/RubyStack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel.rb:285:in `new'
C:/Bitnami/RubyStack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel.rb:285:in `run'
C:/Bitnami/RubyStack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel.rb:268:in `initialize'
C:/Bitnami/RubyStack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel.rb:268:in `new'
C:/Bitnami/RubyStack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel.rb:268:in `run'
C:/Bitnami/RubyStack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:282:in `run'
C:/Bitnami/RubyStack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:281:in `each'
C:/Bitnami/RubyStack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:281:in `run'
C:/Bitnami/RubyStack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:128:in `run'
C:/Bitnami/RubyStack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/command.rb:212:in `run'
C:/Bitnami/RubyStack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:281
C:/Bitnami/RubyStack/ruby/bin/mongrel_rails:19:in `load'
C:/Bitnami/RubyStack/ruby/bin/mongrel_rails:19
Rendering C:/Bitnami/RubyStack/apps/redmine/public/500.html (500 Internal Server Error)
RE: Ticket grouping plugin - Added by Andrew Rudenko about 15 years ago
You're all luckies! I couldn't even migrate plugin. I got the newest version (gzipped tarball) from http://github.com/Ubik/redmine_issues_group (http://download.github.com/Ubik-redmine_issues_group-59d6b245524847df8be7e253f3c341edffdd4689.tar.gz).
Got an error when execute command:rake db:migrate_plugins RAILS_ENV="production"
Migrating redmine_issues_group... == AddQueriesGroupBy: migrating ============================================== -- add_column(:queries, :group_by, :string) == AddQueriesGroupBy: migrated (0.1062s) ===================================== rake aborted! An error has occurred, this and all later migrations canceled: PGError: ERROR: current transaction is aborted, commands ignored until end of transaction block : INSERT INTO schema_migrations (version) VALUES ('1-redmine_issues_group')
detailed info (--trace):
Migrating redmine_issues_group... == AddQueriesGroupBy: migrating ============================================== -- add_column(:queries, :group_by, :string) == AddQueriesGroupBy: migrated (0.0031s) ===================================== rake aborted! An error has occurred, this and all later migrations canceled: PGError: ERROR: current transaction is aborted, commands ignored until end of transaction block : INSERT INTO schema_migrations (version) VALUES ('1-redmine_issues_group') /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract_adapter.rb:219:in `log' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/postgresql_adapter.rb:550:in `execute' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/database_statements.rb:259:in `insert_sql' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/database_statements.rb:44:in `insert_without_query_dirty' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/query_cache.rb:18:in `insert' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/postgresql_adapter.rb:497:in `insert' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/migration.rb:545:in `record_version_state_after_migrating' /var/www/redmine-dev/vendor/plugins/engines/lib/engines/plugin/migrator.rb:39:in `record_version_state_after_migrating' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/migration.rb:487:in `migrate' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/migration.rb:560:in `call' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/migration.rb:560:in `ddl_transaction' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in `transaction' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/transactions.rb:182:in `transaction' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/migration.rb:560:in `ddl_transaction' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/migration.rb:485:in `migrate' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/migration.rb:472:in `each' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/migration.rb:472:in `migrate' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/migration.rb:400:in `up' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/migration.rb:383:in `migrate' /var/www/redmine-dev/vendor/plugins/engines/lib/engines/plugin/migrator.rb:20:in `migrate_plugin' /var/www/redmine-dev/config/../vendor/plugins/engines/lib/engines/plugin.rb:93:in `migrate' /var/www/redmine-dev/lib/tasks/migrate_plugins.rake:8 /var/www/redmine-dev/lib/tasks/migrate_plugins.rake:5:in `each' /var/www/redmine-dev/lib/tasks/migrate_plugins.rake:5 /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /usr/bin/rake:19:in `load' /usr/bin/rake:19
Redmine 0.8.5.devel.2900 (PostgreSQL)
About your application's environment Ruby version 1.8.7 (i486-linux) RubyGems version 1.3.5 Rack version 1.0 Rails version 2.3.4 Active Record version 2.3.4 Active Resource version 2.3.4 Action Mailer version 2.3.4 Active Support version 2.3.4 Application root /var/www/redmine-dev Environment production Database adapter postgresql Database schema version 20090704172358 About your Redmine plugins Redmine Wiki Extensions plugin 0.1.0 Redmine Local Avatars plugin 0.0.2 Redmine Graphs plugin 0.1.0 Issue Due Date 0.1.0 Global filter plugin 0.0.1 Redmine Code Review plugin 0.2.4
I would appreciate any solution to fix this.
RE: Ticket grouping plugin - Added by Andrew Rudenko about 15 years ago
and in addition gems list
*** LOCAL GEMS *** actionmailer (2.3.4, 2.3.2, 2.2.2) actionpack (2.3.4, 2.3.2, 2.2.2) activerecord (2.3.4, 2.3.2, 2.2.2) activeresource (2.3.4, 2.3.2, 2.2.2) activesupport (2.3.4, 2.3.2, 2.2.2) fastthread (1.0.7) passenger (2.2.5) postgres (0.7.9.2008.01.28) postgres-pr (0.6.1) rack (1.0.0) rails (2.3.4, 2.3.2, 2.2.2) rake (0.8.7, 0.8.5, 0.8.3) rubygems-update (1.3.5, 1.3.2)
RE: Ticket grouping plugin - Added by doha rouas about 15 years ago
hi all,
i have just integrated this plugin and it works fine ... great job!!!
however, i would like to organize my tickets.. i want to create subtickets for each one... i have so many tickets opened and i would like to move them as subtickets for others.
how can i do that? is there any plugin for that?
thanks in advance for your help