Details
-
Bug
-
Resolution: Fixed
-
Low
-
None
-
None
Description
There is a screenshot in our docs of Versions and Components in Bulk Move that is now out of date (it was actually out of date before): http://confluence.atlassian.com/display/JIRA/Modifying+Multiple+%28%27Bulk%27%29+Issues#ModifyingMultiple%28%27Bulk%27%29Issues-bulkmove
It needs to be updated to reflect the new interface given to users when mapping version and component fields.
Tokes completed a 3 day spike of JRA-8248 - Bulk Move components and versions
He established that we should be able to implement a feature which allows mapping old project values (for Components, Versions) to new values using multiple edit controls and a simple name matching strategy to preselect the smart choice. This work will be completed in a future iteration.
Story:
http://jdog.atlassian.com/browse/JRADEV-190?atl_token=Tfoo8Rv5kD
See also:
http://jdog.atlassian.com/browse/JRADEV-566
http://jdog.atlassian.com/browse/JRADEV-697
Attachments
Issue Links
- is detailed by
-
JRASERVER-8248 Retain values checkbox for Bulk Move should preserve versions or components based on version and components names
- Closed
- relates to
-
JRASERVER-20535 Add a documentation hit for bulk move and retaining versions when versions have been archived in the target project
- Closed