View Issue Details

IDProjectCategoryView StatusLast Update
0009641mantisbtotherpublic2011-01-07 18:24
Reporterch750536 Assigned Tovboctor  
PrioritynormalSeverityfeatureReproducibilityalways
Status closedResolutionduplicate 
OSVista 
Product Version1.2.0a2 
Summary0009641: 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.

TagsNo tags attached.

Relationships

duplicate of 0012667 closedvboctor Moving issues between projects doesn't update the category 
related to 0005034 closedvboctor On move project you can't specify the category you'd like to move to 

Activities

jreese

jreese

2008-09-22 10:41

reporter   ~0019424

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.