How to move a story to a defect when a custom field in the defect is required but isn't in the Story

Question

We have an issue when moving a Story to a Defect where we have a field called Injected Version in the Defects that is required. If the original Story has no sub-tasks we get the standard screen for the move, and any additional custom fields are displayed so that we can put in the required values. The Injected Version is updated and the move completes successfully.

However, if the Story has subtasks we get the bulk move screen instead of the simple move dialog. Again fields that were missing in the Story are displayed, but they also have the checkbox against them to retain the old value. Unfortunately, the Injected Version, which is a required field has the retain value checkbox checked, but this is also greyed out so that we cannot uncheck it to fill in a value. This blocks us from making the move.

The questions we need answered are:

* Is this the expected behaviour?
* Can we force the standard move dialog to be displayed instead of the bulk move dialog?
* Can we enable the retain value checkbox so that we can uncheck it?
* Is there anything else we can change to enable us to move the issue?

I forgot to mention, this is on JIRA version 8.9.0

Peter Wells · Answer

It does not make sense to have it in the sub-task, especially as the defect is being copied from a Story. The Story's sub-task should not have the field, but neither would the Defect sub-task.

John Funk · Answer

Hi Peter - Is the Injected Version field only available to Defect issue types in the context? If so, maybe if you added it to Sub-tasks as well you might not have it greyed out.