View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009641 | mantisbt | other | public | 2008-09-17 05:42 | 2011-01-07 18:24 |
Reporter | ch750536 | Assigned To | vboctor | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | duplicate | ||
OS | Vista | ||||
Product Version | 1.2.0a2 | ||||
Summary | 0009641: Categories dont get reassigned when moving issues | ||||
Description | If you move issues from one project to another it would be nice if the system helped with reassigning the categories to those in the new project. Currently the categories are still pointing to those in the old project. If identically named issues exist this could be automatic, otherwise it could ask for some mapping to apply. | ||||
Tags | No tags attached. | ||||
This is currently intended behavior, because in the past, the category was never migrated when moving bugs between projects (it was just a string). For the time being, the feeling is that until we can generate a "proper" interface for determining bug category at the time of movement, it is better to keep the old category in place, and let an intelligent updater make the proper decision to change category appropriately, rather than make any (possibly false) assumptions about the new category. The fact that the category is still prefixed with the old project is meant to be an immediate clue to the user that it needs to be updated post-movement. However, it would be beneficial to, at some point, devise and implement a simple method for reassigning bug category during movement. Patches / submissions are welcome, of course. |
|