-
Bug
-
Resolution: Fixed
-
High
-
10.75
-
3
-
Severity 2 - Major
-
Rockets - Usher 8
Issue Summary
When users export a list of Capabilities via the UI and update the owner field to a different email address. Then attempts to import the updated user, the import utility doesn't recognize the users. If you attempt to set the new owner manually through the UI dropdown, the system will recognize the user and update the Capability.
Note: This also affects other work items.
Steps to Reproduce
- Step 1 - Example: Export a capability (ensure there is an existing owner tied to this Capability) this is also impacting all work item imports.
- Step 2 - On the export, template update the owner field to another user with the same permissions and program associations (make sure this user exist in the dropdown via the UI
- Step 3 - Attempt to import the modified Capability
Expected Results
PDM - Will define the expected results
Actual Results
Users can't mass update and modify owners via the import utility
Workaround
Ignore the label indicated on the owner column on the Import template.
The email address of a ...
- relates to
-
JIRAALIGN-1495 [JIRAALIGN-1495] Excel Import: Creating a new Feature/Story/ Test Case or updating an existing Feature/ Story/ Test Case's Owner via the Excel Import does not set the Owner
- Closed
- resolves
-
ALIGNSP-6012 Loading...
-
PS-64051 Loading...