Defect #18541
closedMove issue to another project
0%
Description
Hi
I seem to have stumbled upon a bug in redmine: it seems impossible to move a single issue to another project.
What I do:
- click 'edit' on an issue
- select different project in the drop-down menu
What happens:
- some popup shows for less than a second (so I don’t know what it says)
- the drop-down menu jumps back to the current project
What I expect:
- the drop-down menu to stay on the selected project
- move the issue to the selected project on clicking "submit"
It is, however, possible to move multiple issues to another project by "bulk-editing" them as described below:
- have a list of issues, e.g. 'View all issues' in the project list
- select >1 issue (or you will get to the same page you get to when clicking "edit" in an issue)
- rightclick, edit
- select new project
- click "submit"
I found several other people asking about similar issues in the last few years, but either no solution was provided for them, or the bug was fixed years ago, or the issue was related to a user having multiple, conflicting roles, one allowing him to move issues, the other not. I made sure to avoid such conflicts. References to similar issues I found but which did not seem to have a solution:
(mentioned role-conflict issue)
#6195 (and related #12651 #6391)
#1847 (and related #7447 #2559)
System information:
I’m running redmine on debian testing (jessie) using apache and passenger, exact versions:
redmine 3.0~20140825-1 redmine-pgsql 3.0~20140825-1 postgresql 9.4+163 postgresql-9.4 9.4~beta3-3 ruby-pg 0.17.1-2 ruby 1:2.1.0.4 ruby-rails 2:4.1.6-2 libapache2-mod-passenger 4.0.53-1 ruby-passenger 4.0.53-1
The server was initially set up with debian testing and the mentioned redmine-version just a few weeks ago. No migrations or updates have been made yet. No plugins are installed.
I tried running "script/about", but that only returned this info:
ticket001:/usr/share/redmine# ruby script/about script/about no longer exists, please use bin/about instead.
There is no bin/about in the debian-package though.
Question:
Is this a bug or am I doing anything wrong?
I appreciate any hint at what could be wrong and any pointer to relevant docs. Please tell me if this issue is missing information that might help find a solution. I’m also happy about pointers regarding how to debug an issue like that properly, as I have no idea how to go on.