View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0015230||mantisbt||bugtracker||public||2012-11-23 05:58||2012-11-23 12:06|
|Target Version||Fixed in Version|
|Summary||0015230: When copying issues, it should be possible to select category to avoid inconsistencies|
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|
In my opinion this issue is strongly linked to 0010325.
|Tags||No tags attached.|
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.
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...
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.
Ok, thanks for the confirmation and your efforts so far.
|2012-11-23 05:58||JanHegewald||New Issue|
|2012-11-23 09:55||dregad||Note Added: 0034367|
|2012-11-23 09:55||dregad||Status||new => feedback|
|2012-11-23 09:57||dregad||Relationship added||related to 0010325|
|2012-11-23 11:15||JanHegewald||Note Added: 0034368|
|2012-11-23 11:15||JanHegewald||Status||feedback => new|
|2012-11-23 11:38||dregad||Note Added: 0034369|
|2012-11-23 11:38||dregad||Status||new => confirmed|
|2012-11-23 11:39||dregad||Note Edited: 0034369||View Revisions|
|2012-11-23 12:06||JanHegewald||Note Added: 0034370|