-
Bug
-
Resolution: Unresolved
-
Medium
-
52
-
Severity 3 - Minor
-
28
-
Issue Summary
When a customer is performing a bulk operation to another project using the "Move" action, sometimes non-required fields are shown as required.
Also, some fields like Description will be cleared of any value, ticking 'Retain' does not help and the field is cleared of any entries once the bulk move is completed.
Steps to Reproduce
- text and radio button fields are reported as required during the bulk move from a team managed project -> company managed project even when these fields are not associated with the project screen. Backend condition that is buggy in behavior is notAllInScope i.e custom field is not in the scope of ANY issue context.
Expected Results
Moving issues without non-required fields showing as required.
Populated fields like descriptions should retain their value.
Actual Results
Non-required fields showing as required.
Populated fields like Description are cleared once the move is completed.
This also applies to all other custom fields using the "Text Field (multi-line)" type
Workaround
This typically happens if the destination Project is using a different Field Configuration and the field renderer doesn't match (Default Text Renderer vs Wiki Style Renderer). By adjusting the field renderer so that they match should solve the problem.
- is duplicated by
-
JRACLOUD-77266 Optional custom fields are displayed to be populated during move operation
-
- Closed
-
-
JRACLOUD-78048 When moving an issue to another project or issue type, if the originating project/issue type isn't part of the custom field's context, the CF is presented as a required field
-
- Closed
-
-
JRACLOUD-80494 Optional custom fields marked as required when performing a bulk move operation from one project to another
-
- Closed
-
-
JRACLOUD-95669 Moving work item from team-managed project to company-managed project results removes the description value if the respective wiki renderer is turned off in the field configuration
-
- Closed
-
- is related to
-
JRACLOUD-76989 Bulk move operation displays custom fields of type "version picker" as mandatory even though they are not in destination project
-
- Closed
-
-
JRACLOUD-79050 Moving issues between projects with different field configurations causes fields to pop up in "update fields" if using different renderers
-
- Closed
-
-
JRACLOUD-79655 Asked to update custom fields that share the same settings among projects when moving issues where the field default value in the source project is configured for another issue type
-
- Closed
-
- relates to
-
JRACLOUD-78048 When moving an issue to another project or issue type, if the originating project/issue type isn't part of the custom field's context, the CF is presented as a required field
-
- Closed
-
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...