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

Calculating remaining_hours after plugin migration failure. #1019

Open
dlcron opened this issue Jan 8, 2014 · 0 comments
Open

Calculating remaining_hours after plugin migration failure. #1019

dlcron opened this issue Jan 8, 2014 · 0 comments

Comments

@dlcron
Copy link

dlcron commented Jan 8, 2014

Migration finished with no errors.

0.9.26 -> 1.0.6 (redmine backlogs)
2.0.0 -> 2.3.2 (redmine)

After redmine_backlogs migration the data migrated for purposes of burdawn charts differ. I tried to find solution on my own, getting through RbIssueHistory migration function, but no success. I am sure it's migration fault, because new table was added to store information like remaining hours, and the values there differ.

Can you help me? Screens example:
capture
capture1

Hope it's enough info.
Marcin

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

1 participant