Redmine

+1 I'd like to see one level of grouping (e.g. Group issues by Status). A simple UI that would work is to have a select box with each Filter name and a none (default).

+1, I wrote a note about this in: Issue #2481 as well. The grouping in Trac is excellent.

+1
The Scrumalliance Redmine has a plugin for issue grouping. Not for all attributes, but it's a start...

+1
Could be done as seperate tables per group (though that would be a bit awkward given the Redmine UI style) or using Outlook style grouping bars (with a + or - to expand or collapse the group). Might not even require a Group By field - often grouping issues by the field in the sorted column is enough, and that change could perhaps be accomplished in the view alone?

Ewan Makepeace wrote:

+1
Could be done as seperate table per group (though that would be a bit awkward given the Redmine UI style) or using Outlook style grouping bars (with a + or - to expand or collapse the group). Might not even require a Group By field - often grouping issues by the field in the sorted column is enough, and that change could perhaps be accomplished in the view alone?

Hi, can be this merged into trunk?
I'm not so much big friend of patches, because we're using trunk version by SVN updates.
Thanx!

There are such functionality converted to plugin - http://www.redmine.org/boards/3/topics/4701

Good plugin, the only thing that's stopping me from using it in a productive system is that when you already have a bunch of queries the plugin doesn't seem to work (complains about missing category)...

Markus Knittig wrote:

Good plugin, the only thing that's stopping me from using it in a productive system is that when you already have a bunch of queries the plugin doesn't seem to work (complains about missing category)...

Maybe you don't run db migration, this plugin needs it (I missing this in description):

rake db:migrate_plugins

I have tested installation of this plugin on trunk version and it works without any errors

Hm, this works on my produtive system. Thanks. But it didn't seem to to work with the example data...

Markus Knittig wrote:

Hm, this works on my produtive system. Thanks. But it didn't seem to to work with the example data...

Development, test or demo database migration needed too:

rake db:migrate_plugins RAILS_ENV="development"

This plugin at v0.0.3 looks quite neat. As noted by Eric on the referenced forum-thread it overrides some controllers though, but in the new version this is done pretty smart (which will prevent most of the syncing-problems)... Looks really promising... :thumbsup:

One caveat though: the package contains an error on lines 10 and 11 in the file ../app/views/issues/_sidebar.rhtml. These lines are missing the controller-part in the links. They should be changed from:

  planning_links << link_to(l(:label_calendar), :action => 'calendar', :project_id => @project) if User.current.allowed_to?(:view_calendar, @project, :global => true)
  planning_links << link_to(l(:label_gantt), :action => 'gantt', :project_id => @project) if User.current.allowed_to?(:view_gantt, @project, :global => true)

  planning_links << link_to(l(:label_calendar), :controller => 'issues', :action => 'calendar', :project_id => @project) if User.current.allowed_to?(:view_calendar, @project, :global => true)
  planning_links << link_to(l(:label_gantt), :controller => 'issues', :action => 'gantt', :project_id => @project) if User.current.allowed_to?(:view_gantt, @project, :global => true)

Good work. Have you considered to publish your plugin on GitHub (where most of the Redmine plugins are hosted)? That would make it easier to contribute and kepping the plugin up to date...

Markus Knittig wrote:

Good work. Have you considered to publish your plugin on GitHub (where most of the Redmine plugins are hosted)? That would make it easier to contribute and kepping the plugin up to date...

I wish that functionality of this plugin be included in trunk version, because it can't be implemented separately from Redmine core like other plugins. There is some overridings, which can break plugin in future if core changed.

About plugins and github - I use local svn and don't know git yet, I think that we need to make community for plugin/patches developers with svn/git, Redmine tracker, maybe this can be redminehacks.org

Andrew Chaika wrote:

I wish that functionality of this plugin be included in trunk version, because it can't be implemented separately from Redmine core like other plugins.

Then you should include some tests. Also, I'm not sure about the category feature. In principal It's useful, but I kinda don't like that it's working with free text. Although a own entity might be overkill. A compromise could be some sort of auto completion...

About plugins and github - I use local svn and don't know git yet, I think that we need to make community for plugin/patches developers with svn/git, Redmine tracker, maybe this can be redminehacks.org

I'm sure Eric will take good care of redminehacks.org (which used git and will probably continue to do so)...

Thanx a lot for such a great plugin!
Is there some project page of this plugin?
I would like to close this issue and discuss it probably somewhere more dedicated ;)

Maxim Krušina wrote:

Thanx a lot for such a great plugin!
Is there some project page of this plugin?
I would like to close this issue and discuss it probably somewhere more dedicated ;)

For now only forum thread - http://www.redmine.org/boards/3/topics/4701
I have published version 0.0.5 there

I try to use Git for Windows to upload plugin code to https://github.com, but it's unsuccessful yet

Cool that you final decided to use git. You won't regret it, it's really great... :)
Do you have problems with git on Windows or with GitHub? Because GitHub is IMO really easy to use. Don't know about git on Windows though. That could be tricky. AFAIK msysGit is the best choice under Windows.

Jean-Philippe Lang wrote:

Feature added in r2696.

Really great to see this being merged into the trunk... Just a question:

• the group-folding feature (JS)?
• the queries categories, and grouping by them in sidebar?
• the queries in sidebar shows count of issues in them?

If you are willing to take these things into the core trunk also, the plugin by Andre Chaika can be considered as a solution for issue #2679 for the 0.8-branch while it's implemented in the core for the trunk...

What do you think?

Mischa The Evil wrote:

Would it be also possible to add:

• the group-folding feature (JS)?

Done in r2711.

• the queries categories, and grouping by them in sidebar?

This would be nice, although it's not part of the ticket grouping feature.

• the queries in sidebar shows count of issues in them?

This can really slow things down depending of the number of queries. So I don't think it will be added to the core.

Great that this is implemented!

Perhaps the feature to display ticket associations (parent -> child) like
http://www.redmine.org/boards/3/topics/4701 as Andrew Chaika suggested could be implemented?
This would be really helpful to manage complex implementations or e.g. a feature request which should be implemented in several sub projects.

Or some other way to display such connections would be good.

Jean-Philippe Lang wrote:

Mischa The Evil wrote:

Would it be also possible to add:

• the group-folding feature (JS)?

Done in r2711.

Great... This "sort of" completes the implementation of the ticket-grouping feature in my opinion... Thanks...

Jean-Philippe Lang wrote:

Mischa The Evil wrote:

• the queries categories, and grouping by them in sidebar?

This would be nice, although it's not part of the ticket grouping feature.

True that it's not part of the grouping feature. I'll open a new issue regarding this new feature. If I find the time for it I'll try to look to extract the feature from Andrew's plugin into a new plugin.
Though I believe that (mainly) the UI of the custom filter feature should be optimized (speaking for example of issues #2883, #2002, #3180 and more generally issue #1307) before/during addition of new (UI) sub-features of the custom filter feature in general.

Jean-Philippe Lang wrote:

Mischa The Evil wrote:

• the queries in sidebar shows count of issues in them?

This can really slow things down depending of the number of queries. So I don't think it will be added to the core.

Good point which I haven't though of before... ;)

With kind regards,

Mischa.

Gregor Bader wrote:

Perhaps the feature to display ticket associations (parent -> child) like
http://www.redmine.org/boards/3/topics/4701 as Andrew Chaika suggested could be implemented?

I am not sure if Andrew's solution for sub-issues (as he has implemented it in the ticket-grouping plugin v0.0.7) is sufficient enough to get implemented in the core.
I am certainly not skilled enough to decide (not even to discuss this:), but looking at the comments on issue #443 a sub-issue feature would require a big overhaul of the core's design...
Jean-Philippe once commented that sub-issues wasn't planned (2 months ago) after more people started implementing the feature as a plugin. I don't know if the implementation by Andrew is "sufficient" enough to get implemented into the core neither if Jean-Philippe has the opinion that the feature must get implemented through a plugin or not...

Regards,

Mischa.

Mischa The Evil wrote:

Gregor Bader wrote:

Perhaps the feature to display ticket associations (parent -> child) like
http://www.redmine.org/boards/3/topics/4701 as Andrew Chaika suggested could be implemented?

I am not sure if Andrew's solution for sub-issues (as he has implemented it in the ticket-grouping plugin v0.0.7) is sufficient enough to get implemented in the core.

My implementation is not optimal and I know this, there are lot of subqueries and template recursion in it (one of the solutions is to render subisues only when user expand parent issue through ajax call).
But it works for me and solve my problem. I will try to make it better if I find the means of doing it.

Mischa The Evil wrote:

Gregor Bader wrote:

Perhaps the feature to display ticket associations (parent -> child) like
http://www.redmine.org/boards/3/topics/4701 as Andrew Chaika suggested could be implemented?

I am not sure if Andrew's solution for sub-issues (as he has implemented it in the ticket-grouping plugin v0.0.7) is sufficient enough to get implemented in the core.
I am certainly not skilled enough to decide (not even to discuss this:), but looking at the comments on issue #443 a sub-issue feature would require a big overhaul of the core's design...
Jean-Philippe once commented that sub-issues wasn't planned (2 months ago) after more people started implementing the feature as a plugin. I don't know if the implementation by Andrew is "sufficient" enough to get implemented into the core neither if Jean-Philippe has the opinion that the feature must get implemented through a plugin or not...

Regards,

Mischa.

A new or changed implementation of Subissues isn't needed. Everything that's needed is already there. I mean the blocking association between issues.
This should be possible to display in a tree view as the plugin from Chaika. It's kinda grouping by blocked issues.

Gregor Bader wrote:

A new or changed implementation of Subissues isn't needed. Everything that's needed is already there. I mean the blocking association between issues.
This should be possible to display in a tree view as the plugin from Chaika. It's kinda grouping by blocked issues.

In one of posts Jean-Philippe wrote that issues relations is not designed to implement subissues feature and it's need to use "some kind of nested set" for it.

Grouping by blocked issue with one nesting level is easy to implement (add group field - blocking issue) with current issues grouping feature.

Great to see this feature integrated in the trunk ! One gap: in the plugin version, it was possible to group issues by custom field, in the trunk version (r2711) custom fields don't appear in the "group results by" drop down list ...

loic Le Gallou wrote:

One gap: in the plugin version, it was possible to group issues by custom field, in the trunk version (r2711) custom fields don't appear in the "group results by" drop down list ...

Can you check it with the current trunk and with the info provided in the journals of issue #3321? I guess that if the issue custom field is displayed in the selected issuelist view then it shows up in the "group by"-options too... I am not sure atm, I'll test it soon too...

Regards,

Mischa.

+1 Would be good to see this in 0.9

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

+1 for custom fields. I have also tested on the latest trunk r2967 and find that custom fields are not available to group by even though they are displayed in the issues list table and are available to filter by. This would be very useful for our instance of Redmine. Thanks,
Will

SPAM