-
Suggestion
-
Resolution: Duplicate
-
None
We'd like the ability to chose weather or not to copy/create versions and components when bulk moving issues to a new project. Currently, they need to be manually created in the destination project before Bulk Operations.
Details:
Currently in Jira Software Cloud, when you MOVE an issue (from the issue itself in the MORE menu) that has Versions or Components to a new project - if the destination project does not have these Versions or Components users can either ADD new values or map to existing within the destination project.
Moving One Issue from issue More (...) menu
However, when using Bulk Operations from Filters, even for only one issue, you MUST map to existing values in the destination project. Based on the details on the screen - it almost seems like the values would be created if "retain" is selected.
Moving ONE issue with Bulk Operations
- duplicates
-
JRACLOUD-67933 Allow "Releases"/"Versions"/"Fix Version/s" to be exported/imported into projects
- Gathering Interest