How can you change project category with Jira Automation?

[Josh Fuller]

I am currently the only admin for my team. New projects are created by me, then they team will come in a populate the project. Currently they can do everything themselves except set the project category that we use for sorting dashboards. I have to come back in and change the category upon request.

I am looking to use a custom field they fill out to act as the project category, then use Jira Automation to populate the category based on their selection. My issue is, when I try to use "Set Project Property", it runs successfully but I see no change.

I am using {{issue.fields.project.projectCategory.name}} as the property key and the value comes from a custom field laid out as {{customfield_10204.value}}

Is this a valid approach and if so, where am I going wrong? I've adjusted syntax a couple dozen times and finally decided to write a post here for pointers.

Thanks!

[Nic Brough -Adaptavist- · Accepted solution]

The application log file should have a lot more information on what is going wrong.

[benwatanabe]

Thanks Nic, turned out it didn't have the INDEX permission in the database and that was causing the Agile error. Weird that it didn't cause an equivalent JIRA error.

[Nic Brough -Adaptavist-]

Hmm. At a guess, I'd say you'd installed JIRA with index permissions, and then locked it down later. Or, you might have run into the rather interesting case that JIRA core code would like to index the database, but can work without it, whereas Agile really needs it and fails if it can't do it. (Guessing at this one, of course, but old versions of JIRA didn't create indices on the database, Greenhopper did)