-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
8.3.0, 8.7.0, 8.8.0
-
8.03
-
4
-
Severity 2 - Major
-
1
-
Issue Summary
Bulk Move operation does not retain All the users (or existing active users) if the User Picker (multiple users) custom field contains any inactive users.
Proceeding further with Bulk move provides a retain checkbox, but even after selecting that the presented user fields will be empty and continuing would
overwrite this field with empty values in the target project's issue.
Steps to Reproduce
- Create Project A, Project B
- Create users test1, test2 in Project A.
- Create a Custom Field CC Users with User Picker (multiple users) and add to Project A
- Create a test issue and add test1, test2 to CC users.
- Go to User management and Inactivate the user "test1"
- Perform the Bulk Move operation with Retain Checkbox option selected for CC Users
Expected Results
Issue moved to Target project with all the Users (or Active users) retained.
Actual Results
CC Users will be empty.
Workaround
- Make the inactive users active again and perform the Bulk Move of issues. Once it is completed Inactivate the users again.
- Please test this in a test environment before proceeding further. Also as per Atlassian Support Offerings we would not be able to provide the extended support
on this as it is related to altering database values.SELECT * from cwd_user u join cwd_directory d on u.directory_id = d.id where u.active = 0; --(This is to check the inactive users) select * from public.customfieldvalue where stringvalue in (select user_key from app_user a, cwd_directory d, cwd_user u where d.id=u.directory_id and a.id=u.id and u.active=0) ; --(This is to identify Inactive users associated with Jira issue from CC Users field) delete from public.customfieldvalue where stringvalue in (select user_key from app_user a, cwd_directory d, cwd_user u where d.id=u.directory_id and a.id=u.id and u.active=0) ; --(Deleting these entries would result in successful Move of the issues as all the Active Users are retained as it is)
Encountered this in v9.4.1