Ticket grouping plugin

Added by Andrew Chaika almost 9 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 Nikolay Dranchuk over 7 years ago

i made another version "redmine_issue_grouping"
it works with:
ruby 1.8.7
redmine 0.9.1
windows + mongrel_service.

RE: Ticket grouping plugin - Added by Nikolay Dranchuk over 7 years ago

Nikolay Dranchuk wrote:

i made another version "redmine_issue_grouping"
it works with:
ruby 1.8.7
redmine 0.9.3
windows + mongrel_service.

RE: Ticket grouping plugin - Added by Nikolay Dranchuk over 7 years ago

when updating issue, event posted twice.
How to solved it?

redmine.JPG (8.32 KB)

RE: Ticket grouping plugin - Added by Marco Gutsche over 7 years ago

Roland Discein wrote:

Marco Gutsche wrote:

Marco Gutsche wrote:

Hello,

I've read that subtasking in the new realse will be a core function.
So I've checkout the latest trunk and the database structure looks very similiar (the core has an extra collumn root-id).

Is a migration possible by filling this extra collumn or will it be more work to migrate to redmine 1.0.0?

Thank a lot.

Hello,

has nobody an idea or an hint? :(

current version of a plugin is compatible, but core functions have different behaviour with columns lft and rgt. Also plugin have additional features. My users have got used to use the plugin interface for subtasking, so this code still alive.

Thanks for your answer.
That's bad news that a migration isn't possbible (or hard to handle).
Will the plugin work with 1.0.0? I've found no possibility to turn off the core subtasking?

RE: Ticket grouping plugin - Added by Vitaly Klimov over 7 years ago

I modified original migration file to handle conversion from TicketGrouping plugin to built-in Redmine subtasking. Please copy it over existing one in db\migrate and remove folder(redmine_issues_group) from vendor\plugins folder before actual migration.

WARNING This migration makes irreversible changes to database, so make sure you have backed it up before doing migration.

I have tested it on my production system with 10k issues and MySQL 5, It took about 8 minutes to do migration and all parent->child issues successfully migrated

One more time - please DO backup your database before performing migration - this snippet was not thoroughly tested

Also i have attached Queries Group Plugin which i made from Ticket Grouping plugin for grouping queries by categories because i liked this functionality in Ticket Grouping plugin

RE: Ticket grouping plugin - Added by Tomasz Król over 7 years ago

Hi
I've installed Redmine 1.0.0(RC) and would like to use subtasking a lot (grouping tasks within user stories). It would be great to see the issues like a tasks tree.
Please let me know how to install this plugin as it seems to be outdated and I am not sure if it would work for me.

Thanks in advance.

BTW: if the core allow subtasks, shouldn't it provide an view to see the parent/child structure?

RE: Ticket grouping plugin - Added by Sergey Astakhov over 7 years ago

Nikolay Dranchuk wrote:

when updating issue, event posted twice.
How to solved it?

Николай, приветствую! Вы решили данную проблему?
Если да, то как?

У меня установлен redmine 0.9.6 и этот плагин без патча 17 версии (с патчем пропадают возможность сворачивать группы в основном меню).

Конечно хотелось бы аналогичну работоспособность в версии 1.х. Сделал, как описывал Виталий Климов, но функциональность по сравнению с работой плагина не устроила :(
Есть еще варианты?

RE: Ticket grouping plugin - Added by Roland Discein over 7 years ago

Sergey Astakhov wrote:

Nikolay Dranchuk wrote:

when updating issue, event posted twice.
How to solved it?

Николай, приветствую! Вы решили данную проблему?
Если да, то как?

Обновитесь до 1.0.0 минимум, должно исчезнуть само собой.

RE: Ticket grouping plugin - Added by Sergey Astakhov over 7 years ago

Roland Discein wrote:

Sergey Astakhov wrote:

Nikolay Dranchuk wrote:

when updating issue, event posted twice.
How to solved it?

Николай, приветствую! Вы решили данную проблему?
Если да, то как?

Обновитесь до 1.0.0 минимум, должно исчезнуть само собой.

Николай, не очень понял :)

Судя по всему вышенаписаному и личному опыту (пробывал) в 1.х этот плагин не работает :(
Там есть встроенные подзадачи и группы, но они менее функциональны. Или я не прав?

RE: Ticket grouping plugin - Added by Roland Discein over 7 years ago

Sergey Astakhov wrote:

Roland Discein wrote:

Sergey Astakhov wrote:

Nikolay Dranchuk wrote:

when updating issue, event posted twice.
How to solved it?

Николай, приветствую! Вы решили данную проблему?
Если да, то как?

Обновитесь до 1.0.0 минимум, должно исчезнуть само собой.

Николай, не очень понял :)

Судя по всему вышенаписаному и личному опыту (пробывал) в 1.х этот плагин не работает :(
Там есть встроенные подзадачи и группы, но они менее функциональны. Или я не прав?

У меня установлен trunk 1.0.1 со встроенными подзадачами и поверх него работает этот патченный плагин (выкладывал выше 1.7 patched) - оставил его для функционала группировки запросов по просьбам трудящихся.

Журнал не дублируется.

Недавно обновился до r4068 - перестала работать функция "изменить родителя" из контекстного меню.
Решил так:

# cat vendor/plugins/redmine_issues_group/config/routes.rb 
ActionController::Routing::Routes.draw do |map|
  map.parent_edit 'issues/parent_edit', :controller => 'issues', :action => 'parent_edit'
end

We have working trunk with this plugin v1.7_patched. No journals dupes.

Btw, recently updated to r4068, I noticed the "parent edit" context menu feature was broken.
It shows 404 at /issues/parent_edit?ids[]=XXXX

I fix this with route in config/routes.rb file of plugin's directory:

ActionController::Routing::Routes.draw do |map|
  map.parent_edit 'issues/parent_edit', :controller => 'issues', :action => 'parent_edit'
end

If you unlucky, try to cleanup journals with this bash script in crontab (fill in all vars):

#!/bin/bash
DBUSER="" 
DBPASS="" 
DBNAME="" 
echo "delete t2 from journal_details as t1, journal_details as t2 where t1.journal_id=t2.journal_id and t1.prop_key=t2.prop_key and t2.id>t1.id;"|mysql -u ${DBUSER} -p"${DBPASS}" ${DBNAME} -s

Sergey Astakhov wrote:

Судя по всему вышенаписаному и личному опыту (пробывал) в 1.х этот плагин не работает :(

Какую версию плагина ставите? какая версия redmine? в чём выражается неработоспособность?

RE: Ticket grouping plugin - Added by Ariel Wainer about 7 years ago

Is it possible to use this plugin with Postgres 8.3 as backend?
Running rake db:migrate_plugins returns a MySQL error, which does not makes sense, since I'm not using MySQL.

RE: Ticket grouping plugin - Added by Larry Cai almost 7 years ago

any news on whether this feature exist on latest 1.0.x redmine version

RE: Ticket grouping plugin - Added by Vadym Yarosh almost 6 years ago

Плагин не работает с версией 1.3. После устновки не возможно просмотреть любую задачу - выводится "ошибка 500".
Будет ли дорабатываться поддержка актуальной версии и будущих версий редмайна?

RE: Ticket grouping plugin - Added by Tobias Fischer almost 6 years ago

Larry Cai wrote:

any news on whether this feature exist on latest 1.0.x redmine version

Yep, it's included in 1.3

RE: Ticket grouping plugin - Added by Vadim Tsurkov almost 4 years ago

in version 2.3.x Redmine plugin not workin. :-( Have analog plugin?
у когонить пашет в 2.3.x (если да, то как решили) или есть аналог?

RE: Ticket grouping plugin - Added by Vadim Tsurkov almost 4 years ago

  1. rake redmine:plugins:migrate RAILS_ENV="production"
    (in /usr/share/redmine-2.3)
    rake aborted!
    cannot load such file -- dispatcher

RE: Ticket grouping plugin - Added by Ivan Cenov almost 4 years ago

Why is this plugin?
Redmine 2.5.0 is capable grouping issues by a field.

1 ... 7 8 9 (201-217/217)