Hi All,
So, i am trying to create a new automation flow to populate a custom field with the current assignee for In Progress, this will be used eventually if the issue goes passed In review, and fails in QA, i will use this field to automatically re-assign the issue back to the person populated in my custom field.
But i have created the custom file and cannot find it in automation, even after refreshing my browser.
The type is User Property field and the context configuration is below:
when i go into automation and i try to use edit issue my custom field in not available and i'm lost as to why.
Is it because I have chosen the wrong type and it should be a single user picker?
Thanks
Jeff
If your custom field is indeed a "User Property Field" type, that is an entity property of a user.
Please use the Set Entity Property action, selecting the correct type, user, and property name to set the value: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Set-entity-property
Kind regards,
Bill
Hi @Bill Sheboy,
I tried this, but against doesn't seem to work and populate the field, maybe I set something wrong in the set entity property area?
but here are as many screenshots as I think will help
I'm a lot lost now.
thanks,
Jeff
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I just tried this for that field type with the Set Entity Property action and it works. Let's confirm some things for your scenario:
Please make those changes and re-test your rule.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @jeff_trotman
You can use Advanced Json in edit issues switch to more options and use :
{
"fields": {
"customfield_XXXXX": "{{assignee.accountId}}"
}
}
Hope this is helpfull
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Sirine
I tried this, it is successful, but doesn't populate the field, could the type be wrong?
I've tried User Property field and Single User Picker
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It seems the issue might be with the field type
So make sure your custom field is set to User picker as the User property field may not work with the {{assignee.accountId}}
Try to use {{assignee.id}} instead
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
have you associated the custom fields with your project screens?
When you create or edit an issue are you able to add value (manually) to the custom field?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, it is associated with the project screens and i can see the field in any issue i create, but if i type anything into the field, it errors saying it couldn't update the in progress assignee field
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is the automation in details also under the "enhanced engagement framework" project?
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.
Hi,
If the custom field is not appearing in your automation settings, it may indeed be related to whether the field is included on the appropriate screens
BR
Kai
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is included and I can see the custom field on any issue I create
thanks,
Jeff
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.