-
Type:
Bug
-
Resolution: Timed out
-
Priority:
Low
-
1
-
Severity 3 - Minor
Problem Definition
Component/s field with empty value that is being Bulk Moved from one Issuetype to another on the same Project and the component/s field is required in the field configuration throws an error. The error that is thrown on the Bulk move is due to the required field configuration, however there's no input field that is visible for a value to be entered.
Reproducing the Problem
- Go to your Field Configurations, create two different Field Configurations for each IssueType. example Task and Bug
- Add that Field Configuration to your Field configuration Scheme, then associate that field configuration scheme to your Project.
- First of all, make the component/s field optionals then create some issues
- Create a Task without component field
- Edit your Field configuration and make the component/s field "required" for both Issuetypes.
- Search for these issues using the Issue Navigator. Example JQL below
project = COM AND issuetype= Task AND status not in (Closed, Done) AND component is EMPTY
- Bulk Move this issues from One IssueType to another.
- Error is thrown that the "Component/s field is required" without any input field.
Expected Results
- Since the Component/s field is required, an input field should be visible, so a user can key in a value during the move.
Actual Results
- The Component/s field is required without any Input field. checking on the Dev console shows the input field is hidden after being disabled
<td class=“cell-type-collapsed”> <input id=“retain_components” type=“checkbox” name=“retain_components” value=“” checked=“checked” disabled=“true”> <input type=“hidden” name=“retain_components” value=“true”> </td>
Workaround
- Make the Component/s field optional from the Field Configuration for both Issuetypes.
