0013007: Moving an issue to a sub-project changes the category to the default category - MantisBT - Signup temporarily disabled due to spam

ID	Project	Category	View Status	Date Submitted	Last Update

0013007	mantisbt	sub-projects	public	2011-05-18 03:18	2014-09-23 18:05

Reporter	michael_w	Assigned To	dhx
Priority	high	Severity	major	Reproducibility	always
Status	closed	Resolution	fixed
Product Version	1.2.5
Target Version	1.2.6	Fixed in Version	1.2.6

Summary	0013007: Moving an issue to a sub-project changes the category to the default category
Description	I recently updated to 1.2.5 and now I got the following problem: I have the project A and the sub-project (of A) B. When moving an issue with category C (which is assigned to the project A) to project B, the category gets changed to DEFAULT (configured default category) and doesn't respect the fact, that project B is a subproject of A and does inherit the category C.
Steps To Reproduce	Create two projects: A and B. B is subproject of A Create category C in project A so that B inherits the category. Create issue I in project A Move I to project B Now I has the default category, instead of category C.
Additional Information	This issue is related to: http://www.mantisbt.org/bugs/view.php?id=12667
Tags	patch
Attached Files	patch-hierarchy-inherit-bug-13007.patch (400 bytes) 1091,1092c1091,1092 < // If not global, then attempt mapping it to the new project. < if ( $t_category_project_id != ALL_PROJECTS ) { --- > // If not global and not inheriting the category project, then attempt mapping it to the new project. > if ( $t_category_project_id != ALL_PROJECTS && !project_hierarchy_inherit_parent($p_target_project_id, $t_category_project_id)) { patch-hierarchy-inherit-bug-13007.patch (400 bytes)

michael_w 2011-05-18 03:48 reporter ~0028793	I made a patch for it

atrol 2011-06-02 11:37 developer ~0028901	Reminder sent to: vboctor This is caused by your fix of 0012667 Do you think that the patch from michael_w is Ok?

nimmich 2011-06-28 04:52 reporter ~0029062	Patch works for me.

dhx 2011-07-12 06:05 reporter ~0029143	Sounds reasonable from what I'm reading. Thanks for the patch Michael, I've committed it to master-1.2.x and master branches.

grangeway 2013-04-05 17:57 reporter ~0036384	Marking as 'acknowledged' not resolved/closed to track that change gets ported to master-2.0.x branch

MantisBT: master 21c242c6 2011-07-12 06:03 michael_w Committer: dhx Details Diff	Fix 0013007: Moving an issue to a sub-project - default category used Assume project B is a sub-project of project A. When moving an issue with category C (which is assigned to the project A) to project B, the category gets changed to DEFAULT (configured default category) and doesn't respect the fact, that project B is a subproject of A and does inherit the category C. Steps to reproduce this bug: 1. Create two projects: A and B. B is subproject of A 2. Create category C in project A so that B inherits the category. 3. Create issue I in project A 4. Move I to project B 5. Note that I has the default category instead of category C Signed-off-by: David Hicks <d@hx.id.au>		Affected Issues 0013007
	mod - core/bug_api.php		Diff File
MantisBT: master-1.2.x d0f850da 2011-07-12 06:03 michael_w Committer: dhx Details Diff	Fix 0013007: Moving an issue to a sub-project - default category used Assume project B is a sub-project of project A. When moving an issue with category C (which is assigned to the project A) to project B, the category gets changed to DEFAULT (configured default category) and doesn't respect the fact, that project B is a subproject of A and does inherit the category C. Steps to reproduce this bug: 1. Create two projects: A and B. B is subproject of A 2. Create category C in project A so that B inherits the category. 3. Create issue I in project A 4. Move I to project B 5. Note that I has the default category instead of category C Signed-off-by: David Hicks <d@hx.id.au>		Affected Issues 0013007
	mod - core/bug_api.php		Diff File