Advanced compare condition does not match "projectTypeKey" property on project picker custom field

[Rune Rasmussen]

Setup:

We have a custom field called "Project picker" of the type "Project Picker (single project)".

The https://[Company].atlassian.net/rest/api/3/issue/[Issue] view shows the custom field as having the ID, Key, Name, and Type of project

customfield_10413: {
self: "https://[Company].atlassian.net/rest/api/3/project/10039",
id: "10039",
key: "AAAS",
name: "Atlassian As a Service",
projectTypeKey: "software",
simplified: false,

I want to use this for automated project access and do an "Advanced compare condition" of {{issue.customfield_10413.projectTypeKey}} equals software (or service-desk).

Behaviour

When the project picker custom field has a software project selected and the automation runs the issue does not match the condition.

[Joseph Chung Yin · Accepted solution]

@Rune Rasmussen -

Please give a try of this syntax 

{{customfield_10413.projectTypeKey}}

I also recommend that you can utilize "Log action" when debugging smart value for custom fields in general.  https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Log-action

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

[Rune Rasmussen]

@Joseph Chung Yin 

Thank you for the suggestions.
It turns out that I missed the T in sofTware...

The "Log action" is really neat. Wasn't aware of it, but it'll be a good tool to have going forward.

The syntax of {{customfield_10413.projectTypeKey}} and {{issue.customfield_10413.projectTypeKey}} gives the same value with using the Log action.