Redmine

Second version, added queries groups

Great idea. It would be better if you didn't override the core Redmine controllers. If anything in them change, there's a chance the plugin will break.

Eric

Eric, as I understand the purpose of rails plugins is to demonstrate some functionality without modications of main project code.
I think that issues grouping and queries grouping in sidebar are good extensions (ideas etc.) for the base functionality of Redmine.
There are already some feature requests for such functionality (#2679), that can be solved.
How we can introduce them in the project main stream (trunk version)?
PS Sorry for my ugly english

Andrew Chaika wrote:

Eric, as I understand the purpose of rails plugins is to demonstrate some functionality without modications of main project code.

I'm sorry. For that case of showing how the feature can be implemented, you are right. The majority of Redmine plugins are implemented as separate addons to Redmine that are maintained along with Redmine and I thought this was one of them.

How we can introduce them in the project main stream (trunk version)?

Best way would be to add the patches/plugins to an existing issue or to create a new issue using the Patch tracker. Then we can review it and see about applying the code to the core.

Eric

Hi Andrew,

Please find, attached, the french language files for your plugin:

• ca-fr (lang).yml goes to the lang folder (please rename ca-fr.yml)
• fr (lang).yml goes to the lang folder (please rename fr.yml)
• ca-fr (locales).yml goes to the config/locales folder (please rename ca-fr.yml)
• fr (locales).yml goes to the config/locales folder (please rename fr.yml)

Regards!

Version 0.0.4:

• Added french language files
• Corrected links in sidebar

German translation for the plugins...

Can't install it - froze for a while on db migrate:

rake db:migrate_plugins RAILS_ENV="production"

Migrating engines...
---skipped other plugins---
Migrating redmine_issues_group...

and that's all :(

Redmine 0.8.3 - latest production release

Last version of this plugin works with 0.9 (trunk) version of Redmine.
For 0.8.x branch try to use 0.0.2 version, it was developed and tested on Redmine 0.8.2.
I will check db migration and compatibility with 0.8.3 version.

Very nice plugin. I'm also interested to see if it can be installed in 0.8.3.

The plugin is very usefull, why isn't part of redmine core app?

Version 0.0.5:

• Added Deutch language files
• Added autocompletion for query category field
• Rewritten migrations to be compatible with Redmine 0.8.x (rails 2.1.2)
  It's need to manually destroy group_by and category fields from 'query' table and 'redmine_issues_group' row from 'plugin_schema_info' If you do migrations with 0.0.3-0.0.4 versions on Rails 2.1.2 (Redmine 0.8.x.stable)
• Rewritten query filters for compatibility with Redmine 0.8.3 (no order save)

Tested on Redmine 0.8.0.devel.2641 and Redmine 0.8.3.stable.2670

good plugin!

atached translation for Spanish

Adam Kubica wrote:

The plugin is very usefull, why isn't part of redmine core app?

Now its a part of redmine core since r2696

I have published this plugin at http://github.com/Ubik/redmine_issues_group/tree/origin
In new version I implement Issues List as nested set with some outline view

Great plugin!

Is it compatible with r2711?

Andrew Chaika wrote:

I have published this plugin at http://github.com/Ubik/redmine_issues_group/tree/origin

I can't check it out:
warning: remote HEAD refers to nonexistent ref, unable to checkout.
The default branch on GitHub is master, if your use something differently (like origin) you need to change this in the admin menu...

A workaround is to track the remote branch orgin/orign...

Also Change parent isn't working for me:

NoMethodError (undefined method `issue_categories' for #<Issue:0xb5668ff4>):
    /usr/lib/ruby/gems/1.8/gems/activerecord-2.2.2/lib/active_record/attribute_methods.rb:260:in `method_missing'
    /app/models/issue.rb:100:in `move_to'
...

Markus Knittig wrote:

Also Change parent isn't working for me:

The problem is within issue model it already has method move_to, that implemented in awesome_nested_set.
I have patched my awesome_nested_set (rename 'move_to' method to 'move_to_sub' or something like this), but it's not good solution. Maybe some kind of 'alias_method' will be better, or patch to awesome_nested_set, I will try to fix it.

Is the last version of your plugin also merged with the core of redmine ?

Yohann Monnier wrote:

Is the last version of your plugin also merged with the core of redmine ?

Nope, it isn't. See issue #2679 for implementation details.

Regards,

Mischa

in last version of plugin i have exception in ticket list

NoMethodError in Issues#index

Showing vendor/plugins/redmine_issues_group/app/views/issues/_list.rhtml where line !#44 raised:

undefined method `css_issue_classes' for #<ActionView::Base:0xb6ed18e8>

this was happened in

44:  <tr id="issue-<%= issue.id %>" class="hascontextmenu <%= cycle('odd', 'even') %>
 <%= css_issue_classes(issue) %> group-<%= group_num %>">

change parent method does not correctly processed exception when i have tried to set the parent of issue to himself

ActiveRecord::ActiveRecordError in IssuesController#parent_edit

Impossible move, target node cannot be inside moved tree.

The first exception is because of changes that have made in r2694: http://www.redmine.org/projects/redmine/repository/revisions/2694/diff/trunk/app/views/issues/_list.rhtml
Its need to change css_issue_classes(issue) to issue.css_classes.
The second exception is raised when you try to change parent for list of issues to some subissue of them.
I will correct both errors in next revision.