View Issue Details

IDProjectCategoryView StatusLast Update
0015230mantisbtbugtrackerpublic2012-11-23 12:06
ReporterJanHegewald Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status confirmedResolutionopen 
Product Version1.2.8 
Target VersionFixed in Version 
Summary0015230: 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
  1. Add two projects ("project A" and "project B")
  2. In these projects, create one category respectively (they don't have to have matching names, but it's also no problem if they have)
  3. Create an issue in project A
  4. Copy this issue to project B (the category is now displayed as "[project A] category")
  5. 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.

TagsNo tags attached.

Relationships

related to 0010325 confirmed Move should have the option of changing categories 

Activities

dregad

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

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

dregad

2012-11-23 11:38

developer   ~0034369

Last edited: 2012-11-23 11:39

View 2 revisions

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

JanHegewald

2012-11-23 12:06

reporter   ~0034370

Ok, thanks for the confirmation and your efforts so far.

Issue History

Date Modified Username Field Change
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