Program manager displayname

[Sien Xia]

Hi team,

I'd like to set up a rule for reminding program owner to update ticket automatically, but after I input smartvalue {{program owner.displayname}}, the program owner's name doesn't show on email correctly.

[Bill Sheboy]

Hi @Sien Xia 

What type of project are you using: company-managed or team-managed?  You may find this information at the bottom-left side of the screen expanding area.

And if using a team-managed project, is that a People-type field you have added?  If so, many of the attributes may not be available to rules.  This is a known limitation of this project type.

Also...

Smart values for fields are name, spacing, and case-sensitive, and the often do not exactly match the displayed field name on the issue views.

Please confirm you have the correct smart value for your field with this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Kind regards,
Bill

[Sien Xia]

Thanks Bill! Yeah the weird thing is when I use condition [Scheduled - Query] - [Send email], then program owner smartvalue can show on mail correctly, but when using [lookupissues] - [Send email], mail cannot get the value of Program Owner. displayname. 

[Bill Sheboy]

Just to confirm what you are observing:

• when a rule uses a Scheduled trigger with JQL and references {{issue.Program Owner.displayName}} there is a value, but...
• when a rule gets the issues from a lookup issues action the smart value {{lookupIssues.Program Owner.displayName}} does not for the same Jira issues?

Again, is this a team-managed project's People-type field or a company-managed project's user select field?  

Or...is this field instead provided by a marketplace addon app?

Your project admin and / or Jira site admin can help answer those questions.

Did you try that how-to article to confirm the smart value for the field, or try using its custom field id value instead?

[Sien Xia]

Hi Bill,

Situation confirmed. I check [Program Ower] and found it's a custom field, so that's the reason it doen't work?

If it is, is there any similar action to sort out the list and send to somebody?

[Bill Sheboy]

Let's confirm some things:

1) Are you using Jira Cloud, Jira Server, or Jira Data Center?

If you are using Jira Server or Data Center, the Lookup Issues action does not support most fields, including custom fields yet: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877

In that case, the workaround is to call the REST API issue search with JQL and the Send Web Request action, as that should provide all of the fields.

2) If you are using Jira Cloud, is this a Company-Managed or Team-Managed project?  You can find that information at the bottom-left side of the screen expanding area.

[Sien Xia]

Thanks @Jack Brickey , not sure why it still doesn't work.

[Jack Brickey]

Hi @Sien Xia ,

Could you try  {{issue.program owner.displayname}}?

[Bill Sheboy]

Hi @Jack Brickey 

Based on the rule shown and inside of the Lookup Issues iterator, the issue prefix would not be used.

Kind regards,
Bill

[Jack Brickey]

yes good point... TMP is a likely suspect