-
Notifications
You must be signed in to change notification settings - Fork 460
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
the plugin can support higher redmine version. #1153
Comments
Hello, I have the same question if this plugin is ever going to become compatible with |
who can help me? can you have aother useful version?tkx. |
I almost got this working on redmine 4. Check out wyplay's fork - https://github.com/wyplay/redmine_backlogs.git it almost works, you need to change the ActiveRecord::Migration parts to have a version -
and you need to remove the unnecessary 3 database commits in 012_migrate_legacy.rb - ActiveRecord::Base.connection.commit_db_transaction run the migrate -
then if it fails with a dependent index_issues_on_position error, just drop that index and re run the migrate. Then it at least installs, unfortunately it then complains in the config page in the browser -
and the log says -
|
If you edit "plugins/redmine_backlogs/lib/backlogs_setup.rb" and comment out the def migrated? stanza like this -
then at least you can get into the settings page. errors following that appear to be partly due to not having any data in the tables in the database though. |
Hi FooBarTrixbell, The "errors following that" means like this?
I got this error when i click "Backlogs" tab. |
I'm afraid to say, I was only looking at this as a proof of concept for the boss. He wanted an option for migrating away from Jira. In the end he wasn't overly fond of redmine so we didn't put any serious effort into making it work. I would start by running that query on your database and seeing what SQL error you get -
It looks to me like it is generating incorrect sql as CASE versions.sprint_start_date WHEN NULL THEN 1 ELSE 0 END ASC, will probably generate "Order by 0" or "Order by 1" which is just rubbish. probably doesn't happen when your DB is full though. Perhaps grep for that line in the code and just comment it out, I don't see a reason for it anyway as the order by should not fail if there is nothing to order by. |
Looks like it is in plugins/redmine_backlogs/app/models/rb_sprint.rb
Perhaps change this to
And try again? |
hmm, perhaps not, that ends up in ORDER BY releases.release_start_date DESC, releases.name DESC, releases.release_end_date ASC, releases.release_start_date ASC' and it doesn't like having the release start date in there twice! |
I could only get this to progress by disabling the sort function entirely -
at which point it is happy with the query (I think) but complains about labels.yaml being missing A quick copy of the default file -
and now it just gives a very generic error and I'm stumped, sorry. Let me know if you progress it any! |
Thank you very much for you a lot of research. Unfortunately, I couldn't solve this problem with and another error has emerged. i will keep trying another way. |
redmine‘s version is 3.4.5 now. and the rails version usual is v4.2. and the ruby version is usual is v2.3 up.
but the "redmine_backlogs" is only support ruby 1.9 & 2.0? can up it for higher version? like version 3.4.3 3.4.5? tkx.
The text was updated successfully, but these errors were encountered: