View Issue Details

WikiRelated ChangesetsJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0012667mantisbtbugtrackerpublic2011-01-07 15:442011-09-16 11:03
Reportervboctor Assigned Tovboctor  
PriorityhighSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.2.3 
Target Version1.2.5Fixed in Version1.2.5 
Summary0012667: Moving issues between projects doesn't update the category
Description

If an issue with category GUI is moved from Project A to Project B (where both have the category defined as non-global), then the issue will show the category name in the view page as "[Project A] GUI" even though the issue now belongs to project B. Also if the user edits the issue, the first category is selected from the list since "[Project A] GUI" is not a valid entry.

The proposed fix is as follows:

  1. If the category is global, then leave as is.
  2. If the category has a match by name in the target project, then switch to that.
  3. If the category doesn't have a match by name in the target project, then move a configured default global category (by default "General").
TagsNo tags attached.

Relationships

Relationship GraphDependency Graph
related to 0005034 closedvboctor On move project you can't specify the category you'd like to move to 
related to 0010325 confirmed Move should have the option of changing categories 
related to 0006763 closedvboctor when try to "move" an issue, only "project" can be changed, however, there is no way to update "category" 
has duplicate 0007518 closedvboctor Move issue with specified category to project without categories 
has duplicate 0004671 closedvboctor Problems with categories after issue move 
has duplicate 0009641 closedvboctor Categories dont get reassigned when moving issues 
has duplicate 0012896 closedatrol Issues are moved without updating the category-id 
related to 0013233 new Allow status change upon moving tickets to another project 

Activities

There are no notes attached to this issue.

Related Changesets

MantisBT: master-1.2.x a25d69fc

2011-01-07 15:55

vboctor


Details Diff		 Fix 0012667: Moving issues between projects doesn't update the category

If an issue with category GUI is moved from Project A to Project B (where both have the category defined as non-global), then the issue will show the category name in the view page as "[Project A] GUI" even though the issue now belongs to project B. Also if the user edits the issue, the first category is selected from the list since "[Project A] GUI" is not a valid entry.

The proposed fix is as follows:

1. If the category is global, then leave as is.
2. If the category has a match by name in the target project, then switch to that.
3. If the category doesn't have a match by name in the target project, then move a configured default global category (by default "General").		 Affected Issues
0012667
mod - bug_actiongroup.php Diff File
mod - docbook/adminguide/en/configuration.sgml Diff File
mod - config_defaults_inc.php Diff File
mod - core/bug_api.php Diff File

MantisBT: master 8e303d2c

2011-01-07 15:55

vboctor


Details Diff		 Fix 0012667: Moving issues between projects doesn't update the category

If an issue with category GUI is moved from Project A to Project B (where both have the category defined as non-global), then the issue will show the category name in the view page as "[Project A] GUI" even though the issue now belongs to project B. Also if the user edits the issue, the first category is selected from the list since "[Project A] GUI" is not a valid entry.

The proposed fix is as follows:

1. If the category is global, then leave as is.
2. If the category has a match by name in the target project, then switch to that.
3. If the category doesn't have a match by name in the target project, then move a configured default global category (by default "General").		 Affected Issues
0012667
mod - docbook/Admin_Guide/en-US/Configuration.xml Diff File
mod - bug_actiongroup.php Diff File
mod - core/bug_api.php Diff File
mod - config_defaults_inc.php Diff File