I have a user name stored in plain text in a smart value.
Is there a way using Project Automation to convert that into a jira usable format (with the account ID I believe) and assign a ticket, change reporter, etc using this smart value?
Any assistance appreciated.
Cheers
Oliver
Given my business case, I only had 3 possible users. Ended up doing a branching "If {{username}} = X, assign to X". Inelegant and un-scalable but works in this case.
Hello @Oliver Scott-Hughes (CX)
Thank you for reaching out.
I'm not sure if I completely understood your request, but it seems you are trying to copy the value from some field to the assignee field of your issue using Smart values, considering the username instead of accountId. Is that correct?
If that's what you are trying to do, I would say this is not possible as Jira REST API does not reference usernames anymore. Only the accountID can be referenced in Jira automation due to the GDPR implementation (See this documentation for more details).
To have a little more context about what you are trying to do, can you please give us more details on what do you mean with the following sentence?
I have a user name stored in a smart value eg mine would be "Oliver Scott-Hughes".
I know that you can reference a value from a specific field using smart values, however, I'm not aware of a smart value function that can be used to store it. Can you give us more details about this?
Also, only user picker fields can be copied to other user pickers (Assignee). Actually, you can add other field formats (as Text, number, select list) to user pickers, however, they must be explicitly added with the accountID parameter, otherwise, it should not work.
That being said, you can reference a value from another User field as the assignee by using the smart value {{assignee.accountId}}
. Let me give you a practical example:
Let's suppose you have a user picker field called "test user picker" and you want the user added in this field to become the assignee when the issue is done. You can use the following automation rule:
For more details on how to handle user picker fields with smart values, you can check the documentation below:
Let us know if you have any questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.