Team-Managed Automation Limitations - Can't Use People Picker Fields

[Eric J Trumbull]

Hello, 

I am building an automation for one of our teams that uses a team-managed work management project. I have run into an issue where I can't copy the people value from one of the fields they made due to the automation limitations in TM projects.

I'm curious what other folks have done to get around this.

I can just create a global custom field and then copy of the value of the tm custom field to the global custom field with an automation rule This feels clunky and I'm curious if you have other ideas!

https://support.atlassian.com/cloud-automation/docs/limitations-in-team-managed-projects-for-automation-rules/

[Bill Sheboy · Accepted solution]

Hi @Eric J Trumbull 

Without seeing the specifics of your automation rule(s)...

Team-managed project's People fields are often not shown in the field dropdown lists of rule actions.  However, they can be accessed / set using advanced edit with JSON and their custom field ids.  To learn more about using JSON for edits, please look here:

• https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/
• https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

People fields do have a problem where there is no emailAddress attribute available to rules for such field types.  Here is the suggestion to fix that: https://jira.atlassian.com/browse/AUTO-519

Kind regards,
Bill

[John Funk]

There's also this one: https://jira.atlassian.com/browse/AUTO-421

[Eric J Trumbull]

@John Funk - thanks, I've voted and am watching!

@Bill Sheboy - thank you! I appreciate the direction. This should me accomplish my objective.