I cannot find my custom field in automation

[jeff_trotman]

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

[Bill Sheboy · Accepted solution]

Hi @jeff_trotman 

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

[jeff_trotman]

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

[Bill Sheboy]

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:

• For the "Property key", the rule sets it to a custom field value, but that must be static as it was defined when you created the field.  Please enter the correct value.
• For the "Property value", the rule sets it to a JSON expression.  I recommend only setting it to the {{assignee.accountId}} value as that is what will be needed when you reference the property later.

Please make those changes and re-test your rule.

[jeff_trotman]

@Bill Sheboy 

The property key is 10618 as confirmed by the url when i go into the custom field screen

For the "Property value", the rule sets it to a JSON expression.  I recommend only setting it to the {{assignee.accountId}} value as that is what will be needed when you reference the property later. - do you mean this?

Could you share your set up, I think that would help.

Thanks,

Jeff

[jeff_trotman]

One thing I did see, was an email from JIRA saying that

[Bill Sheboy]

An example would be as I described earlier:

• action: Set entity property
  • Entity type: User
  • Select a user: Work Item Assignee
  • Property key: myUserPropertyKey
  • Property value: {{issue.assignee.accountId}}

For your case, "Property key" would likely be:

in progress assignee

That must exactly match the field setup name and case, or it could be creating new properties with different names. 

You may check that by looking at the properties using a browser tab and the REST API endpoint: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-user-properties/#api-rest-api-3-user-properties-get

For example, using your assignee's account ID try this:

yourJiraURL/rest/api/3/user/properties?accountId=yourAccountId

Then search on the page for your key, and any similar ones that may have been added.

And, I have observed problems in rules when the Property Key has spaces or dashes in the name.

[jeff_trotman]

I tried all the things you said @Bill Sheboy , but I just cannot get the field populated, I have a ton of other work piling up, which i need to get on with, so I'm giving up for the moment, I'll revisit this at a later stage.

I'll put yours as the accepted answer, as from what i can tell seems to be the right path.

Thanks for your time,

Jeff

[Vishal Biyani]

@jeff_trotman 

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?

[jeff_trotman]

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

[Calvin]

Is the automation in details also under the "enhanced engagement framework" project?

[jeff_trotman]

Yep, its all there and all visible

[Kai Krause]

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 

[jeff_trotman]

It is included and I can see the custom field on any issue I create

thanks,

Jeff