-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
5.12.0
-
1
-
Severity 3 - Minor
-
Issue Summary
Assets Jira user attribute can be set to User key or User name, but cannot be set to email. This means if email is used, the search falls back to the slower full name search will not resolve.
Steps to Reproduce
- Configure an Assets attribute with a Jira user
- Add a Jira user to User management
- Create a CSV import with a User email column
- Configure the Jira user Data locator to be the user email
Expected Results
The import should find the Jira user
Actual Results
The import cannot find the user.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Versions Tested
Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below:
Testing Requirements | Version | Affected Version |
---|---|---|
Customers Reported Version | Example: 9.14.2 | (Yes / No) |
Most Recent Bug-Fix Release | ||
Previous Major Release | ||
Most Recent LTS | ||
Previous Supported LTS | ||
Other Versions.. | ||
(Add rows as needed) |
- links to
Form Name |
---|