Want hide field options basis customer request type

[SysAdmin]

Hi,

I want to hide options of a single select field based on the customer request type on portal create form.

The field options should vary depending on the customer request type.

When we open the portal window for a particular request type the visible field options should be limited as mapped.

Need help in doing this, we have JSM v5.4.1.

Kindly can anyone guide with this?

Regards,

[David Nickell]

Good afternoon.   I am well versed in field configuraions but not so much with form fields.

So I am sharing what I asked ChatGPT and it's response. I hope this helps you, but also points out ChatGPT can be very helpful in answering these types of questions.

I asked:

in Jira, custom fields have a concept of "context" which allows me to establish different options in a drop down based on issue type (as an example). this is done in a field configuration scheme, What about fields on a request? do form fields support configuraion context?

---

Response:

Short answer: Yes for Jira custom fields, No (not in the same way) for JSM Form fields — but there are workarounds.

Do JSM Form fields support field configuration contexts?

→ No. Form-created fields do not use Jira custom field contexts.

Do Jira custom fields used on the portal respect their contexts?

→ Yes. If the request type is tied to an issue type, the custom field’s context applies.

Do JSM Forms offer alternatives?

→ Yes:

• Conditional logic for field visibility

• Data Connections (Premium+) for dynamic lists

• Separate form layouts per Request Type

---

Then I asked a few follow up questions and it comes down to this:

Yes, you can use a single custom field with different option sets per Issue Type on the portal IF you have one Request Type per Issue Type.

But NO, Request Types cannot be used directly as context drivers.
Contexts only key off Issue Type and/or Project — never Request Type.