Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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

Eric J Trumbull May 22, 2024


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!



1 answer

1 accepted

0 votes
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 22, 2024

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:

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:

Kind regards,

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 23, 2024

There's also this one:


Like Bill Sheboy likes this
Eric J Trumbull May 23, 2024

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

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

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events