Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Burndown chart display wrong information at print version #1009

Open
drscream opened this issue Dec 10, 2013 · 2 comments
Open

Burndown chart display wrong information at print version #1009

drscream opened this issue Dec 10, 2013 · 2 comments

Comments

@drscream
Copy link

Environment:
  Redmine version                2.3.4.stable.12353
  Ruby version                   2.0.0-p247 (2013-06-27) [x86_64-linux]
  Rails version                  3.2.13
Redmine plugins:
  redmine_backlogs               v1.0.6

The information displayed on the burndown chart and the print version looks different.

burndown_nv

The left side shows the print version the right side the embedded graph. After calculation the ideal path from my side (multiply all estimation hours) there is something wrong at the print version.

Also some background information, i'm migrated the redmine from version 1.3.2.stable and backlogs v0.9.3 to the above version.

@holgerfriedrich
Copy link
Contributor

I can confirm the issue, same for us.

Environment:
Redmine version 2.3.2.stable
Ruby version 1.9.3-p194 (2012-04-20) [i486-linux]
Rails version 3.2.13
Environment production
Database adapter Mysql2
Redmine plugins:
redmine_auto_percent 0.0.1
redmine_backlogs v1.0.5
redmine_code_review 0.6.3
redmine_dmsf 1.4.5p1 stable
redmine_etherpad 0.0.1
redmine_http_auth 0.3.0-dev-redmine-2.x
redmine_issue_checklist 2.0.5
redmine_private_wiki 0.2.2
redmine_projectstyle 0.0.2
redmine_wiki_extensions 0.6.4
redmine_wiki_gchart_formula 0.0.5
wiking 0.0.4

Best, Holger

@misccold
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants