Check project category in validator - groovy script

[fjodors]

Hello

I need to check issue's project category in workflow validator

I think that the best way is check it using groovy script.

Trying to execute

issue.projectObject.category == 'CategoryName'

it returns error: javax.script.ScriptException: groovy.lang.MissingPropertyException: No such property: category for class: com.atlassian.jira.project.ProjectImpl

Is there any command to get and check project category in validator?

Thanks,

Fyodor

[Jozef Kotlár · Accepted solution]

See javadoc and use issue.projectObject.projectCategoryObject.name == 'CategoryName' instead.

[JamieA]

Probably want to be null-safe there... not all projects have a category: issue.projectObject.projectCategoryObject?.name == '...'

[fjodors]

Hello Thank you for assistance. issue.projectObject.projectCategoryObject?.name == '...' works. Fyodor

[Patrick Norris]

I am needing to do this same validation in Jira Cloud JMWE.  Unfortunately, the syntax of the command is not the same and I can't find any documentation other than this thread that could help steer me in the right direction.  The closest I've gotten is:  issue.project.properties.projectCategoryObject.name == "..." which returns:

Evaluation failed: "issue.project.properties.projectCategoryObject.name" - Unrecognized property of `issue.project.properties.projectCategoryObject`: "name" ('name'). Type null does not have any properties

And, without the ".name" node, it simply returns a "null" value.  I've also tried .categoryName and .id (testing for the category value) which return a similar error as above.

Does anyone happen to know the syntax for Jira Cloud JMWE?  Any help would be greatly appreciated.

[David Fischer]

Unfortunately, Jira expressions don't provide access to project category information: https://developer.atlassian.com/cloud/jira/platform/jira-expressions-type-reference/#project

This is a limitation of Jira Cloud, not JMWE. The limitation will be the same for all apps. 

[Patrick Norris]

Thanks for your quick feedback, David!  Greatly appreciated!