I noticed something when moving issue from one issue type to another in the same project and I am not sure if this is an issue.
Case 1: An issue has no sub tasks.
I tried to move this issue and in one of the move screens i was able to see the "Affects version" field and i could select the value for it while moving.
Case 2: As issue has at least 1 sub-task.
I tried to move this issue but i was not able to see the "Affects version" field to select value (also a few other fields were not listed).
Is this the expected behaviour in Case 2? I am assuming JIRA considers it as a multiple issue move.
For the target issue type we have "Affects version" as a mandatory field so we are unable to move issue in case 2.
I understand that we can set issue with the value of Affects version and then move, but just wanted to know if this is the expected behaviour although the move is within the project.
Note : JIRA Version 6.3.1
Thank you in advance.
I just tried case 1 and case 2 as you mentioned and have moved the issues successfully.However, I got some errors if the fields are empty or not filled in source issue. I could notice while moving the issues JIRA checks only mandatory fields to be updated if they are not filled and all other fields are updated automatically with default values in target issue.
And that doesn't matter if there is a sub-task to an issue or not, it will be moved along with the parent issue as everything remains same within the project.
The error that displays on the screen will precise what the issue actually, as JIRA throws an error if it cannot fetch/found a particular field.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot