-
Bug
-
Resolution: Not a bug
-
Medium
-
None
-
8.0.5
-
None
-
Severity 3 - Minor
Summary
Automation rules fails to execute and audit log shows Some Errors when using Smart Value
initiator.displayName, The behavior is observed in case Display Name and Full Name are not identical
Steps to Reproduce
- Create a automation rule and a User picker Custom field
- Choose a trigger of your choice, for e.g. Transitioning an issue
- Add an Edit Issue action in rule to update the custom field created in #1
- Use initiator.displayName for updating the value in custom field
- Perform an action which triggers the rule, with a user with different Full Name and UserName For e.g. Full Name is Charlie C while Username is Charlie
- Verify the audit logs, the request will fail with below errors:
Error editing issues EP-7 (User 'Charlie C' was not found in the system. (customfield_id))
Expected Results
Automation rule should run successfully and should be updating the issue based on Username
Actual Results
Automation rule fails with user errors since it looks for users Full Name
Workaround
Using Smart-Value initiator.name can help to achieve some similar requirement
We are closing this ticket because it's indeed the username not the display name that is used to identify a user in Jira.
It's not possible to uniquely determine a user with just display name.