Redmine

Great idea! Thanks a lot!

We love this plugin, especially the settings section to choose the trackers and statuses to be shown.

About the new feature announcements on Github: when do you plan a new release with for instance:
- ability to sort on Issue # / description / start date and/or end date
- maybe take parent child relations into account?

Thanks for your Plugin and time put into this!

I'm getting the following error over and over again. Any advice?

Migrating redmine_scrumdashboard...
2 Dashboardstatuses: migrating ===========================================
-- create_table("dashboard_statuses")
-> 0.1121s
rake aborted!
Mysql::Error: Table 'dnwtechc_redmine.dashboards' doesn't exist: SELECT * FROM `dashboards`

Thanks

Hi.

I get an error message as below.

"stack level too deep"

I have no idea what went wrong with that. Currently I'm using :

- Redmine 0.8.4 revision 2778
- Windows xp sp3
- MySQL 5.0.33

Please check if you guys can give me any of advise or solution for the problem above.

Thank you.

I can't seen the configuration page of the Dashboard after activating the module.

The Apache log says:

ActiveRecord::StatementInvalid (Mysql::Error: Table 'redmine.dashboards' doesn't exist: SELECT * FROM `dashboards`     WHERE (project_id = 1)  LIMIT 1):
    /vendor/rails/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb:147:in `log'
    /vendor/rails/activerecord/lib/active_record/connection_adapters/mysql_adapter.rb:302:in `execute'
    /vendor/rails/activerecord/lib/active_record/connection_adapters/mysql_adapter.rb:537:in `select'
    /vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in `select_all_without_query_cache'
    /vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:59:in `select_all'
    /vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:80:in `cache_sql'
    /vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:59:in `select_all'
    /vendor/rails/activerecord/lib/active_record/base.rb:586:in `find_by_sql'
    /vendor/rails/activerecord/lib/active_record/base.rb:1345:in `find_every'
    /vendor/rails/activerecord/lib/active_record/base.rb:1307:in `find_initial'
    /vendor/rails/activerecord/lib/active_record/base.rb:538:in `find'
    /vendor/plugins/redmine_scrumdashboard/app/controllers/dashboard_controller.rb:210:in `get_globals'
    /vendor/plugins/redmine_scrumdashboard/app/controllers/dashboard_controller.rb:22: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 `passenger_orig_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 `passenger_orig_perform_action'
    /usr/lib/ruby/site_ruby/1.8/passenger/railz/request_handler.rb:53: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'
    /usr/lib/ruby/site_ruby/1.8/passenger/railz/request_handler.rb:38:in `process_request'
    /usr/lib/ruby/site_ruby/1.8/passenger/abstract_request_handler.rb:165:in `main_loop'
    /usr/lib/ruby/site_ruby/1.8/passenger/railz/application_spawner.rb:321:in `start_request_handler'
    /usr/lib/ruby/site_ruby/1.8/passenger/railz/application_spawner.rb:282:in `handle_spawn_application'
    /usr/lib/ruby/site_ruby/1.8/passenger/utils.rb:163:in `safe_fork'
    /usr/lib/ruby/site_ruby/1.8/passenger/utils.rb:161:in `fork'
    /usr/lib/ruby/site_ruby/1.8/passenger/utils.rb:161:in `safe_fork'
    /usr/lib/ruby/site_ruby/1.8/passenger/railz/application_spawner.rb:280:in `handle_spawn_application'
    /usr/lib/ruby/site_ruby/1.8/passenger/utils.rb:163:in `safe_fork'
    /usr/lib/ruby/site_ruby/1.8/passenger/utils.rb:161:in `fork'
    /usr/lib/ruby/site_ruby/1.8/passenger/utils.rb:161:in `safe_fork'
    /usr/lib/ruby/site_ruby/1.8/passenger/railz/application_spawner.rb:279:in `handle_spawn_application'
    /usr/lib/ruby/site_ruby/1.8/passenger/abstract_server.rb:317:in `__send__'
    /usr/lib/ruby/site_ruby/1.8/passenger/abstract_server.rb:317:in `main_loop'
    /usr/lib/ruby/site_ruby/1.8/passenger/abstract_server.rb:168:in `start_synchronously'
    /usr/lib/ruby/site_ruby/1.8/passenger/abstract_server.rb:135:in `start'
    /usr/lib/ruby/site_ruby/1.8/passenger/abstract_server.rb:112:in `fork'
    /usr/lib/ruby/site_ruby/1.8/passenger/abstract_server.rb:112:in `start'
    /usr/lib/ruby/site_ruby/1.8/passenger/railz/application_spawner.rb:179:in `start'
    /usr/lib/ruby/site_ruby/1.8/passenger/spawn_manager.rb:222:in `spawn_rails_application'
    /usr/lib/ruby/site_ruby/1.8/passenger/spawn_manager.rb:217:in `synchronize'
    /usr/lib/ruby/site_ruby/1.8/passenger/spawn_manager.rb:217:in `spawn_rails_application'
    /usr/lib/ruby/site_ruby/1.8/passenger/spawn_manager.rb:126:in `spawn_application'
    /usr/lib/ruby/site_ruby/1.8/passenger/spawn_manager.rb:251:in `handle_spawn_application'
    /usr/lib/ruby/site_ruby/1.8/passenger/abstract_server.rb:317:in `__send__'
    /usr/lib/ruby/site_ruby/1.8/passenger/abstract_server.rb:317:in `main_loop'
    /usr/lib/ruby/site_ruby/1.8/passenger/abstract_server.rb:168:in `start_synchronously'
    /usr/lib/passenger/passenger-spawn-server:46

Redmine 0.8.4

Have you remembered to do a db migrate before using the plugin?

- rake db:migrate_plugins

Is this the only problem you are experiencing with the plugin? Is it possible to see the contents on the dashboard, move issues around and so on?

I still haven't tested the plugin with Redmine 0.8.4, so I really appreciate that people report bugs like this, so I've got something to fix when I get time to do it. I've been kinda busy lately, but I hope I'll get some time to fix some bugs soon.

Hi

I'm ussing current trunk and I cannot see the link to the configuration page too. I can assure that I did run rake db:migrate_plugins and that I have dashboard and dashboard_* tables. Nonetheless, there's no link in the "Dashboard" section

This is waht I have in production.log

Processing DashboardController#index (for xxxxx at 2009-07-20 18:22:22) [GET]
  Parameters: {"action"=>"index", "id"=>"xxx", "controller"=>"dashboard"}
Rendering template within layouts/base
Rendering dashboard/index

Hmm. This is really strange. Are you logged in as administrator? The admin users are the only users that are allowed to see the plugin's configuration page.

Yes, I'm using a user with administrator's rights.

If you need any debug info, just ask, I'd like to solve this issue. Remember that as I said I'm not using 0.8.x but current trunk.

Maybe it's related to the newer translation system? Cause I get

"translation missing: en, label_dashboard"

as the dashboard's header

That sounds like it could be the problem (or another problem at least). I'm going to look into it when I get some time to do it. Hopefully I'll be able to fix it in a couple of days or so. I've recently moved so I don't got my main test server online at the moment. I'll let you know if I need any more debug information when I look deeper into it. Thank you for pointing me in the correct direction :)

Davide Ferrari wrote:

Maybe it's related to the newer translation system? Cause I get

"translation missing: en, label_dashboard"

as the dashboard's header

Mats Klepsland wrote:

That sounds like it could be the problem (or another problem at least).

This is (at least) the problem I reported earlier at http://github.com/thus/redmine-scrumdashboard-plugin/issues/#issue/1.
But, when I tried the plugin the first time using an older trunk-version (so not 0.8.x) I met some other issues too IIRC. I'll try to test it on the trunk again later this week...

Kind regards,

Mischa.

Davide Ferrari wrote:

Hi

[...] I cannot see the link to the configuration page too. I can assure that I did run rake db:migrate_plugins and that I have dashboard and dashboard_* tables. Nonetheless, there's no link in the "Dashboard" section [...]

This is what I have in production.log

> Processing DashboardController#index (for xxxxx at 2009-07-20 18:22:22) [GET]
> Parameters: {"action"=>"index", "id"=>"xxx", "controller"=>"dashboard"}
> Rendering template within layouts/base
> Rendering dashboard/index
> 

Mats Klepsland wrote:

Hmm. This is really strange. Are you logged in as administrator? The admin users are the only users that are allowed to see the plugin's configuration page.

Davide Ferrari wrote:

Yes, I'm using a user with administrator's rights.

This seems to be a documentation issue to me since the "configuration page" is documented as being accessible "through the "Dashboard" link in the top menu of Redmine, and then by clicking the ‘Settings’ button in the top right corner" (quote from: http://github.com/thus/redmine-scrumdashboard-plugin/blob/6d74edfbf6a071a35b509a2adb9ababa29726846/README.rdoc, under "Configuration", third paragraph). This seems also the place where Davide is looking for the missing link considering the log-output.
Though, this is not the correct place where the plugins configuration is located; on the trunk (not 0.8.x) you can find it at: Administration -> Plugins -> Configure (http://host.network.tld/admin/plugins) behind the preferred plugin.

HTH,

Mischa.

Mischa, the Scrum Dashboard plugin doesn't have a configure button/link in the plugins administrator panel. See the jpeg I attach

You are right Davide. There is no configure page in the plugins administrator panel. We encountered problems when trying to add our configuration page to the plugins administrator panel, so we choose to add it to the dashboard page instead. I added a screenshot that points out the position of the configuration link on the dashboard page.

I might try to move the configuration page to the correct location in the future. We were pressed on time when we developed the plugin, so that is why we added it where we did.

I just tested the dashboard using the current trunk. There is a problem with the translation system as you pointed out, but I don't seem to have any problem seeing the settings link. All the "translation missing" messages appearing everywhere on the dashboard and settings page renders the plugin kinda useless with this version of Redmine anyway.

I haven't gotten the time to test the plugin more than this at this time, but it looks to me that there are several more problems with using the plugin with the current trunk.

The funny thing is that the text on the settings link looks like one of the few translations that actually work :p

I'm almost done making the plugin work with the l18n module now. All that remains is testing it, implementing it and off course uploading the new version to GitHub. I would hopefully get this done tomorrow. It's going to be a relief to close the bug reported on GitHub two months ago (This is actually going to be the first update being done to the plugin since then).

I found another critical bug when testing the plugin with the current trunk, so the plugin will still not be "usable" with this version of Redmine yet. This update is only meant as a step in the right direction. The plugin will hopefully be compatible with the current trunk in a future not too far ahead.

Ok I have a news for the topic. I have enabled the scrum dashboard in 2 projects and I see the settings button only in the second project which is by the way a subproject of the 1st. I think this si the problem/bug. The settings button is present only in subprojects, not in main projects (just tried now with another couple, the same: only in the subproject)

I tried to replicate the problem by creating several projects and sub-projects, but I didn't encounter the problem as long as all the projects had at least one version. Does all of your projects have versions attached to them? The settings-link doesn't appear if there is no versions attached to a project. I just added to my todo-list to change so that the link is visible even if there are no versions.

Just committed a new version of the plugin to GitHub with the following change:

- Added l18n support

This is one step towards getting the plugin to work with the current branch of Redmine while still working with the stable branch :)

The plugin just works fine. the first time i did the rake db:migrate_plugins RAILS_ENV=production , the migration was a success. However now, if every-time i do a new rake db:migrate_plugins RAILS_ENV=production i have got the following message:

Migrating redmine_repo_pygments...
Migrating redmine_scrumdashboard...
== 1 ScrumdashboardSetup: migrating ===========================================
-- create_table("dashboards")
rake aborted!
Mysql::Error: Table 'dashboards' already exists: CREATE TABLE `dashboards` (`id`
 int(11) DEFAULT NULL auto_increment PRIMARY KEY, `project_id` int(11) DEFAULT 0
 NOT NULL, `maintracker_id` int(11)) ENGINE=InnoDB
C:/Chr/apps/redmine/vendor/rails/activerecord/lib/active_record/connecti
on_adapters/abstract_adapter.rb:147:in `log'
C:/Chr/apps/redmine/vendor/rails/activerecord/lib/active_record/connecti
on_adapters/mysql_adapter.rb:302:in `execute'
C:/Chr/apps/redmine/vendor/rails/activerecord/lib/active_record/connecti
on_adapters/abstract/schema_statements.rb:108:in `create_table'
C:/Chr/apps/redmine/vendor/rails/activerecord/lib/active_record/connecti
on_adapters/mysql_adapter.rb:438:in `create_table'
C:/Chr/apps/redmine/vendor/rails/activerecord/lib/active_record/migratio
n.rb:346:in `send'
C:/Chr/apps/redmine/vendor/rails/activerecord/lib/active_record/migratio
n.rb:346:in `method_missing'
C:/Chr/apps/redmine/vendor/rails/activerecord/lib/active_record/migratio
n.rb:326:in `say_with_time'
C:/CHR~1/ruby/lib/ruby/1.8/benchmark.rb:293:in `measure'
C:/Chr/apps/redmine/vendor/rails/activerecord/lib/active_record/migratio
n.rb:326:in `say_with_time'
C:/Chr/apps/redmine/vendor/rails/activerecord/lib/active_record/migratio
n.rb:342:in `method_missing'
C:/Chr/apps/redmine/vendor/plugins/redmine_scrumdashboard/db/migrate/001
_scrumdashboard_setup.rb:5:in `up_without_benchmarks'
C:/Chr/apps/redmine/vendor/rails/activerecord/lib/active_record/migratio
n.rb:280:in `send'
C:/Chr/apps/redmine/vendor/rails/activerecord/lib/active_record/migratio
n.rb:280:in `migrate'
C:/CHR~1/ruby/lib/ruby/1.8/benchmark.rb:293:in `measure'
C:/Chr/apps/redmine/vendor/rails/activerecord/lib/active_record/migratio
n.rb:280:in `migrate'
C:/Chr/apps/redmine/vendor/rails/activerecord/lib/active_record/migratio
n.rb:455:in `migrate'
C:/Chr/apps/redmine/vendor/rails/activerecord/lib/active_record/migratio
n.rb:445:in `each'
C:/Chr/apps/redmine/vendor/rails/activerecord/lib/active_record/migratio
n.rb:445:in `migrate'
C:/Chr/apps/redmine/vendor/rails/activerecord/lib/active_record/migratio
n.rb:373:in `up'
C:/Chr/apps/redmine/vendor/rails/activerecord/lib/active_record/migratio
n.rb:356:in `migrate'
C:/Chr/apps/redmine/vendor/plugins/engines/lib/engines/plugin/migrator.r
b:23:in `migrate_plugin'
C:/Chr/apps/redmine/config/../vendor/plugins/engines/lib/engines/plugin.
rb:122:in `migrate'
C:/Chr/apps/redmine/lib/tasks/migrate_plugins.rake:8
C:/Chr/apps/redmine/lib/tasks/migrate_plugins.rake:5:in `each'
C:/Chr/apps/redmine/lib/tasks/migrate_plugins.rake:5
C:/CHR~1/ruby/lib/ruby/gems/1.8/gems/rake-0.8.2/lib/rake.rb:621:in `call'
C:/CHR~1/ruby/lib/ruby/gems/1.8/gems/rake-0.8.2/lib/rake.rb:621:in `execute'
C:/CHR~1/ruby/lib/ruby/gems/1.8/gems/rake-0.8.2/lib/rake.rb:616:in `each'
C:/CHR~1/ruby/lib/ruby/gems/1.8/gems/rake-0.8.2/lib/rake.rb:616:in `execute'
C:/CHR~1/ruby/lib/ruby/gems/1.8/gems/rake-0.8.2/lib/rake.rb:582:in `invoke_wi
th_call_chain'
C:/CHR~1/ruby/lib/ruby/1.8/monitor.rb:238:in `synchronize'
C:/CHR~1/ruby/lib/ruby/gems/1.8/gems/rake-0.8.2/lib/rake.rb:575:in `invoke_wi
th_call_chain'
C:/CHR~1/ruby/lib/ruby/gems/1.8/gems/rake-0.8.2/lib/rake.rb:568:in `invoke'
C:/CHR~1/ruby/lib/ruby/gems/1.8/gems/rake-0.8.2/lib/rake.rb:2031:in `invoke_t
ask'
C:/CHR~1/ruby/lib/ruby/gems/1.8/gems/rake-0.8.2/lib/rake.rb:2009:in `top_leve
l'
C:/CHR~1/ruby/lib/ruby/gems/1.8/gems/rake-0.8.2/lib/rake.rb:2009:in `each'
C:/CHR~1/ruby/lib/ruby/gems/1.8/gems/rake-0.8.2/lib/rake.rb:2009:in `top_leve
l'
C:/CHR~1/ruby/lib/ruby/gems/1.8/gems/rake-0.8.2/lib/rake.rb:2048:in `standard
_exception_handling'
C:/CHR~1/ruby/lib/ruby/gems/1.8/gems/rake-0.8.2/lib/rake.rb:2003:in `top_leve
l'
C:/CHR~1/ruby/lib/ruby/gems/1.8/gems/rake-0.8.2/lib/rake.rb:1982:in `run'
C:/CHR~1/ruby/lib/ruby/gems/1.8/gems/rake-0.8.2/lib/rake.rb:2048:in `standard
_exception_handling'
C:/CHR~1/ruby/lib/ruby/gems/1.8/gems/rake-0.8.2/lib/rake.rb:1979:in `run'
C:/CHR~1/ruby/lib/ruby/gems/1.8/gems/rake-0.8.2/bin/rake:31
C:/CHR~1/ruby/bin/rake:19:in `load'
C:/CHR~1/ruby/bin/rake:19

Any Idea?

I think I found the problem. It is a problem with the plugins migrate files. When you run migrate for the second time the migrate stops because it doesn't expect the tables to already be there. I'll look a little deeper into to it, but it looks like just forcing it to create the tables would fix the problem. I have to test that I don't screw up other parts of the code with this fix, so it would probably be a couple of hours before the fix is committed to GitHub.

Just committed a new version of the plugin to GitHub with the following change:

- Fixed migrate problem.

Mats Klepsland wrote:

I tried to replicate the problem by creating several projects and sub-projects, but I didn't encounter the problem as long as all the projects had at least one version. Does all of your projects have versions attached to them? The settings-link doesn't appear if there is no versions attached to a project. I just added to my todo-list to change so that the link is visible even if there are no versions.

You're definetily right, Mats. The Settings button appears only if there is at least one version, I didn't have any version in the main projects so it didn't work. If it is a feature as I think it is (it's scrum, right? :) ) please add it to the doc so people won't be scared in the future :)

Thanks for your good work!

Davide Ferrari wrote:

Mats Klepsland wrote:

I tried to replicate the problem by creating several projects and sub-projects, but I didn't encounter the problem as long as all the projects had at least one version. Does all of your projects have versions attached to them? The settings-link doesn't appear if there is no versions attached to a project. I just added to my todo-list to change so that the link is visible even if there are no versions.

You're definetily right, Mats. The Settings button appears only if there is at least one version, I didn't have any version in the main projects so it didn't work. If it is a feature as I think it is (it's scrum, right? :) ) please add it to the doc so people won't be scared in the future :)

Thanks for your good work!

That was a relief to hear! I'm going to change it as soon as I can so that the settings button is visible all the time regardless if there are any versions or not. Lets not waste the administrators time by first making him setup the plugin and later have him configure it when the first versions are created! He should be able to do both things at once :)