Details
-
Suggestion
-
Resolution: Won't Do
-
None
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Steps to Reproduce
- Create 2 projects with their own individual field configuration.
- 1 Project(source project) will have a field hidden(in this example we are using the 'Components') field.
- Create issue with a component set in the source project
- Move issue to the project where the 'Components' field is set to be hidden by the field configuration
Expected Results
- The UX of the confirmation screen highlights clearly any potential loss of data from the existing issue.
Actual Results
- The confirmation screen lists out field values that will be removed in the same fashion as those that have been mapped correctly and thus obscures the results to be confirmed.
Field value getting removed can be seen during the last step of the move operation.
Original Description:
When a field is hidden in that target project that is not hidden in the source project, the field will be set to its default value upon the move. In this case the user is presented with the information "All fields can be moved" even though some information will be lost. For example, moving issues into a project where the component field is hidden will silently delete all the components.
Attachments
Issue Links
- relates to
-
JRACLOUD-16607 The confirmation screen on moving issues does not highlight potential information loss clearly
- Closed