View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007206 | mantisbt | administration | public | 2006-06-16 14:08 | 2007-05-08 03:43 |
Reporter | jfirestone | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | closed | Resolution | no change required | ||
Product Version | 1.0.3 | ||||
Summary | 0007206: Ability for Management/Administrator to change "Project" of bug. | ||||
Description | I'd love to be able to change the project of a bug without having to into the DB to alter it. It's not a matter of training people. I have a lot of different projects in the project dropdown, and frequently Reporting an issue winds up placing the issue in the incorrect project when someone's in a hurry. I'd like to see this changeable by a Manager or Admin on demand, with a note on why it was altered. If anyone's actually written code to do this, I have yet to find it. And if folks feel the feature exists, I can't seem to find it. This feature would also help when I need to place a ticket in a sub-project of the main project it was reported in. | ||||
Tags | No tags attached. | ||||
related to | 0004227 | acknowledged | Roadmap 1.0 - Templates |
Click the "Move Issue" button. Its the second to last in the row of buttons below the issue details, above the relationships and the notes. |
|
Excellent, thanks. For some reason, that button's really hidden in the middle of the screen. ;D Perhaps some UI reconfiguring is in order. Feel free to close this issue. |
|
Agreed -- took me awhile to see it too, when I was first looking for the feature. I think the wording "Move Issue" isn't the best, though "Change Project" is unclear in other ways. It also doesn't help that it's after the issue description, which for moderately-sized descriptions means you have to scroll to see it. I agree that a substantial UI redesign is in order, and am hopeful that this can occur once 0004227 is done. |
|