Defect #7584
closed
Can't change priority of moved bug
0%
Description
When I dupe a issue and then move it to another project, I can't change priority of duped bug in the new place! This is very annoying.
Updated by Etienne Massip about 14 years ago
Can't reproduce, could you give more details ? Do you have some plugins installed ?
Updated by teh fink about 14 years ago
I also have the same problem: priority of moved/copied tasks is greyed out.
- Redmine 1.1.1.stable (SQLite)
- ruby 1.8.7 (2010-12-23 patchlevel 330) [i686-darwin10]
I don't have any plugins installed, AFAIK. What details or debugging should I do?
Updated by Etienne Massip about 14 years ago
The priority field state is dependent upon the following test :
:disabled => !@issue.leaf?
From source:trunk/app/views/issues/_attributes.rhtml#L10.
Which could mean either that:- your moved task now has some subtasks attached to it ?
- there is a bug updating issue hierarchy when moving issues
Updated by pasquale [:dedalus] about 14 years ago
Etienne Massip wrote:
Which could mean either that:
- your moved task now has some subtasks attached to it ?
Yes, it is!
Updated by Etienne Massip about 14 years ago
So, as I understand it, this is not an issue due to moving the bug but is part of the #443 subtasking feature : a parent task priority is not changeable as it is the highest priority of its children.
Isn't it ?
Updated by pasquale [:dedalus] about 14 years ago
- Status changed from New to Resolved
Etienne Massip wrote:
So, as I understand it, this is not an issue due to moving the bug but is part of the #443 subtasking feature : a parent task priority is not changeable as it is the highest priority of its children.
Isn't it ?
Ok, I read bug #443: my ticket can be closed as Invalid, because redmine work as aspected.
Updated by Etienne Massip about 14 years ago
- Status changed from Resolved to Closed
- Resolution set to Invalid
Done !