nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Service Desk Automation cant select custom field?

Timothy Harris

I am creating an automation based on a query. If the "IF" statement is true I want to set a custom field to a specific value. But I can't select the custom field?

It is available on the issues and has a global context? The user is the project administrator...

This is JIRA cloud.

Accepted answers

All comments

Ignacio Pulgar

Yeah, only a few system fields can be edited through SD automation rules.

Depending on your needs, maybe you can achieve what you need through a built-in post function.

Otherwise, maybe there's a post function that might help you in the JMWE addon.

Timothy Harris

That's kind of crazy. If you have a custom field on an SD issue. I don't see why in the world you would not be able to set it during an automation rule. Is this just a cloud restriction or is this also the same on server?

Ignacio Pulgar

I bet that's the same on Server, but there you have many more plugin options for automating stuff, like ScriptRunner.

Holly Meza

We are running ServiceDesk on it's own server as a trial and have the same limitation.

Definitely bizarre.

Dave LIAO

As a workaround (at least with recent versions of Jira Service Desk), you can set the automation rule with "Issue matches", choose Advanced, then enter the JQL that the automation should trigger on. Hope this helps someone!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-service-desk

jira-service-desk-cloud

jira-cloud

jira-core