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.

[Olha Yevdokymova_SaaSJet]

Hi @SysAdmin 
In Jira Service Management Data Center, the native portal unfortunately doesn’t support conditional logic inside Jira fields. A single-select field can vary per request type, but you can’t dynamically hide or show specific options depending on the request type.

What’s possible natively:

• Create separate request types with different custom field contexts (each context has its own option set), or

• Use different custom fields per request type.
  But conditional dropdown options inside the same field aren’t supported on DC.

If you want to avoid duplicating fields, a form-based workflow can help.
Smart Forms for Jira (Data Center) supports conditional logic inside the form itself—so you can show or hide fields or entire sections based on the user’s selections. It won’t change the native JSM “Create Request” screen, but it lets you collect structured data with logic applied after the issue is created.

Just to set expectations correctly:

• Smart Forms DC cannot hide options in Jira native fields.

• Forms can be added to issues, including JSM issues, but they are not shown on the initial portal screen.

• And it can be shared externally via a link, so if you don’t want every request to start in the portal, you can collect the data outside Jira and still attach it to the issue automatically.

[Ram Kumar Aravindakshan _Adaptavist_]

Hi @SysAdmin

This is a frequently asked question that has been addressed multiple times in the Community. There are multiple examples for this in the Community forum.

You must use ScriptRunner's Behaviour Initialiser for this.

I have provided a detailed explanation for this requirement in this Community Post.

Let me know how it goes.

Thank you and Kind regards,

Ram