0015230: When copying issues, it should be possible to select category to avoid inconsistencies - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0015230	mantisbt	bugtracker	public	2012-11-23 05:58	2012-11-23 12:06

Reporter	JanHegewald	Assigned To
Priority	normal	Severity	minor	Reproducibility	always
Status	confirmed	Resolution	open
Product Version	1.2.8

Summary	0015230: When copying issues, it should be possible to select category to avoid inconsistencies
Description	Copying an issue leads to the following situation: the category is displayed as "[old project name] category" and when updating the issue, the category is automatically set to whatever is the first category in the category list of the new project if no other category is selected. This might be avoided by asking the user to select a category of the new project when copying the issue.
Steps To Reproduce	Add two projects ("project A" and "project B") In these projects, create one category respectively (they don't have to have matching names, but it's also no problem if they have) Create an issue in project A Copy this issue to project B (the category is now displayed as "[project A] category") Update issue --> the category is changed to whatever is the first category in the category list of project B
Additional Information	In my opinion this issue is strongly linked to 0010325.
Tags	No tags attached.

dregad 2012-11-23 09:55 developer ~0034367	Hello Jan, Just to clarify, are you talking about the 'Clone' function, or the 'Move' function ? Unless I'm mistaken, there is no way to copy an issue into another project in a single step.

JanHegewald 2012-11-23 11:15 reporter ~0034368	Hello dregad, sorry for being not precise enough in the issue description. I am talking about the 'Copy' function on 'View Issues' page, which is located in the drop down field at the bottom of this page. I hope this helps...

dregad 2012-11-23 11:38 developer ~0034369 Last edited: 2012-11-23 11:39	Never realized this could be done in a single step from the view issues page. I confirm the behavior as described (on 1.2.12 also), and agree that the way we currently implement the issue move/clone deserves some improvement.

JanHegewald 2012-11-23 12:06 reporter ~0034370	Ok, thanks for the confirmation and your efforts so far.