Defect #6195
closed
Missing move issues between projects
Added by Marcello Henrique over 13 years ago. Updated over 13 years ago.
100%
Description
Redmine 1.0.1.devel.4035 (MySQL)
Logeed with admin, attached file.
Files
| hide_move_issues.png (92.5 KB) hide_move_issues.png | Marcello Henrique, 2010-08-23 19:15 | ||
| Screen_shot_2010-08-23_at_18.56.46.png (27.6 KB) Screen_shot_2010-08-23_at_18.56.46.png | Sergey Belov, 2010-08-23 19:54 | ||
| move_issues_work.png (110 KB) move_issues_work.png | Marcello Henrique, 2010-08-24 13:13 | ||
| 0001-refs-6195-Missing-move-issues-between-projects.patch (1.6 KB) 0001-refs-6195-Missing-move-issues-between-projects.patch | Masato Igarashi, 2010-08-25 06:10 |
Related issues
Updated by Sergey Belov over 13 years ago
Did you check settings for "Allow cross-project issue relations" ?
Attached screenshot from settings page (this option is unchecked on screenshot)
Updated by Eric Davis over 13 years ago
- Assignee deleted (
Eric Davis)
Please describe the bug, I don't understand what is missing.
Updated by Marcello Henrique over 13 years ago
- File move_issues_work.png move_issues_work.png added
- Assignee set to Eric Davis
Ok, Attached now the same issue but reverted to version "Redmine 1.0.0.devel.3923 (MySQL)" in this version "move" and "copy" is ok. The problem is that new version "Redmine 1.0.1.devel.4035 (MySQL)" is that functions don't appear. I'm highlighting red selected in picture...
Hugs.
Updated by Paulo Santos over 13 years ago
Indeed, I'm having the same problem, the Copy and Move options are now missing on Redmine 1.0.1.
Updated by Eric Davis over 13 years ago
- Assignee deleted (
Eric Davis)
Please don't assign me to an issue.
Updated by Masato Igarashi over 13 years ago
- File 0001-refs-6195-Missing-move-issues-between-projects.patch 0001-refs-6195-Missing-move-issues-between-projects.patch added
Attached a patch for this problem. Please check it out.
Updated by Paulo Santos over 13 years ago
The patch works great, thanks Masato!
It should now be deployed into next version 1.0.2, right?
Updated by Marcello Henrique over 13 years ago
Sorry Eric, you can assign it to roadmap 1.0.2 as patch issue or apply in the code?
Thanks!
Updated by Mario Scondo over 13 years ago
I can confirm that the bugfix is working.
A hint: When trying to move issues assigned to a tracker that is not available for the target project an error is displayed. But there is no message/reason available why moving failed. Is this working 'as designed'?
Updated by Anonymous over 13 years ago
I can confirm this bug exists for me running 1.0.1. I have permission to move issues however the 'Move' and 'Copy' buttons top-right do not show when viewing an issue.
Updated by Jon Lumpkin over 13 years ago
I am also having this issue. I did notice it will show up when you right click an issue in the issue list though. I am running 1.0.1.
Using the one in the issues menu worked fine, but was confusing since its missing on the issue page now.
Updated by Eric Davis over 13 years ago
- Status changed from New to 7
- Assignee set to Eric Davis
- Target version set to 1.0.2
- Affected version (unused) set to 1.0.1
- Affected version set to 1.0.1
Masato Igarashi wrote:
Attached a patch for this problem. Please check it out.
Thanks, but I'm moving Redmine away from using that kind of routing. This should be fixed in link_to_if_authorized.
Updated by Eric Davis over 13 years ago
- Status changed from 7 to Resolved
- % Done changed from 0 to 100
- Resolution set to Fixed
I've changed link_to_if_authorized to allow url paths. This will fix the Move and Copy links on the issue page. r4064
Updated by Eric Davis over 13 years ago
- Status changed from Resolved to Closed
Applied in changeset r4064.
Updated by Eric Davis over 13 years ago
- Status changed from Closed to Reopened
Eric Davis wrote:
Applied in changeset r4064.
The svn comment auto closed this, still needs to be merged for 1.0.2.
Updated by Eric Davis over 13 years ago
- Status changed from Reopened to Resolved
(Wish I could edit the workflows here)
Updated by Eric Davis over 13 years ago
- Status changed from Resolved to Closed
Merged into 1.0-stable for release in 1.0.2
Updated by Yuri Tarasov over 13 years ago
- Assignee deleted (
Eric Davis)
We faced with this problem again in 1.0.2.
Can somebody help?
Updated by Go MAEDA over 13 years ago
Updated by Erik Högstrand over 13 years ago
Masato Igarashi wrote:
Attached a patch for this problem. Please check it out.
I applied that patch on 1.0.2 (local) and it works. It has been applied to trunk, but not to 1.0.2 as stated...
Updated by Remo Laubacher over 13 years ago
Same here, still not merged in 1.0.5.
Can't reopen this issue as it's connected to a closed version.
Any idea how to merge this into the next release?
It's a pity that an already fixed bug is still there..
Updated by Jean-Baptiste Barth over 13 years ago
It has been reverted, see attached revisions (r4257). I think it won't be integrated in a stable branch until we have identified the edge cases, and especially solved problems raised in related issues..