Referencing a Custom Field in JQL

[Robert Werner]

I created a custom field in 3 JIRA projects called "Organizations" to mirror the built-in "Organizations" field in Jira Service Desk.

Using Jira Automation, I've successfully built a rule that correctly sets "Organizations" depending on certain criteria.  This works perfectly!

Now I'm trying to expand the JQL Condition such that it doesn't set it again if it's already set.  I've tried several things to reference my customer "Organizations", whose Custom Field Id = 10538.  But nothing I've tried works.

Any ideas what the proper syntax is?

Robert

[Alexey Matveev]

You should begin to type Organizaions and you will be able to see 2 fields. Then choose your custom field

[Robert Werner]

Yes, that works in that portion of Automation.  But I'm specifically looking to see how I reference the Organizations custom field in JQL.

[Alexey Matveev]

You reference it the same way as in Automation. Just type it in the search text field.

[Robert Werner]

I don't think we're talking about the same thing.  This is the JQL dialog in Jira Automation.  Notice that there's no place to search for "Organizations".  I even double-checked by clearing this text and typing "Organizations" (without the quotes) but it did not recognize it.

[Alexey Matveev]

Ah, ok. This plugin is called Automation For Jira. I just checked it and I also was not able to work with two fields with the same name there. I guess, you would need to change the name of your "Organizations" custom field.

[Robert Werner]

Thanks, Alexey.  I will try creating an "Organization" field for my three non-JSD projects and see if that allows me past this obstacle.

[Robert Werner]

@Alexey Matveev : Thank you for your patience.  I just created an "Organization" field to replace my custom "Organizations" field.  This solved the problem.

Here's one of my sample JQL queries which only sets the field if it is empty:

organization IS EMPTY AND (summary ~ "starbucks" OR description ~ "starbucks")

Two notes for others:

1. The custom field can be written in case-insensitive manner.
2. The custom field can be written with or without quotes.