Currently, I configured my JIRA Bug (issue type) tix with a custom field called Assigned QA.
Problem Statement - I want to create an automation rule for Bug (issue type) tix to set Assigned QA = Reporter of Ticket.
Thanks
Hello @snehil.mishra
Have you tried to construct this rule using the available Automation Rules documentation?
Please show us what you have so far, and let us know with which part you need help.
Sorry I missed to share the screenshot earlier. I set the rule but it is not working.
Logic I added
reporter = issue.reporter();
customField = issue.customFields.getByName('Assigned QA');
if (customField == null) {
issue.assignee = reporter;
} else {
issue.assignee = customField.value;
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @snehil.mishra
When you use the More options to edit a field it is expecting JSON code. Refer to
https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/
Additionally, when you use that option you don't select the field from the pull-down list above.
But you don't actually need to use that option at all.
Instead, modify your rule as follows:
Keep the Trigger and the Condition to check the Issue Type.
Remove all the code that you added under More Options
Click into the field value entry space under Assigned QA (1). In my example screen I chose Assignee because I don't have an Assigned QA field.
Type in the smart value to get the account ID from the issue's Reporter field (1).
After typing in the smart value, click the area below where is says Smart value '{{issue...}}' (2). Clicking there will finish inserting the smart value into the value entry field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.