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; } } }

Can I building condition in A4J that check if certain field is exist in issue screen or not?

Eliyahu Klein --CNTR

Hi,

I want to build a global automation rule that uses an 'If/Else condition' component to fill a specific field only if the field exists on the issue screen. Else - If the field does not exist, the rule should not attempt to fill it.

Currently, I am encountering an error message: 'The set fields may be unavailable for this project/type'

How can I build this rule correctly?

Screenshot 2025-02-11 174827.png

Accepted answers

All comments

Bill Sheboy

Hi @Eliyahu Klein --CNTR

That is likely possible by calling the REST API endpoint (with the Send Web Request action) to get the create issue metadata for the specific project and issue type, and checking if the "set" operation is available. Other than checking for a single field, that seems quite elaborate just to prevent a rule error.

Another alternative is if you know the issue type, the rule could use dynamic JSON to add (or not add) the field.

Kind regards,
Bill

John Funk

Hi Eliyahu,

You should add a context to the custom fields so that they only apply to the appropriate projects and/or issue types first. That will enhance performance for your system and will take care of the need to try to handle with the automation rule.

Eliyahu Klein --CNTR

Hi @Bill Sheboy

Thank you for your response. I appreciate the suggestions you provided. Could you please elaborate and provide examples on how to implement each of the two alternatives you mentioned?

Using the REST API:
- Could you provide a detailed example of how to set up the "Send Web Request" action to call the REST API endpoint and check if the "set" operation is available for a specific field?
Using Dynamic JSON:
- Could you explain where and how to use dynamic JSON to add (or not add) the field based on the issue type? An example would be very helpful.

Thank you for your assistance!

Kind regards,
Eliyahu

Eliyahu Klein --CNTR

Hi @John Funk ,

Thank you for your response. I checked the context for the custom fields, and it seems to be set correctly. However, I am still encountering the error message in the automation rule: "The set fields may be unavailable for this project/type."...

Eliyahu Klein --CNTR

Bill Sheboy

I recommend performing the research necessary for either of these methods, and then experimenting to try them. As a reminder, the Atlassian Community is a place for people to learn and collaborate. It is not a source to provide turnkey solutions upon demand. Please work with your Jira Site Admin to learn more.

Regarding sources to get you started trying those suggestions...

1) Please read this article on calling the Jira REST API endpoints from a rule: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828

Then review the REST API endpoints to learn how to find the issue metadata: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/

2) Using rule conditions or conditional logic, your rule could build a dynamic JSON expression for the specific fields, storing that in a created variable. Here are some sources to help learn how to do that:

John Funk

You still need to add the field(s) to the Edit screen (and/or Create screen). They just won't run for the issue types/projects that are not in the context.

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-cloud