Dynamic show/hide fields on internal create issue screen

[Sebastian Krzewiński]

Hi

I'm looking for a solution that I will be able to show/edit fields dynamically based on select field. I was able to make it for request forms on portal via forms but I want to make similar thing for internal create screen. Is it somehow possible?

Regards,
Seba

[Priyanka Khare]

Hello @Sebastian Krzewiński 

In Jira Cloud, dynamic field visibility (like showing/hiding fields based on a select field) is only available on portal request forms using Forms. Unfortunately, this isn't natively supported on the internal issue create screen.

To achieve similar functionality internally, you'd need to use a third-party app like:

• ScriptRunner for Jira Cloud
• Forge (custom app development)
• Dynamic Forms for Jira

These can help simulate conditional logic on internal screens.

Hope that helps!

[Sebastian Krzewiński]

Hi @Priyanka Khare ! Thanks for your comment.

Unfortunately Dynamics forms and Script runner (I'm thinking about behaviours here) are not working for JSM projects. Forge is not what I'm interested at this moment.

[Olha Yevdokymova_SaaSJet]

Hi @Sebastian Krzewiński 

In native Jira, dynamic show/hide for fields is available in JSM portal forms (like you mentioned), but the standard Create Issue screen doesn’t support conditional logic out of the box. Field visibility there is static — you’d need custom scripts or apps to make it behave dynamically.

A practical workaround is to use Smart Forms for Jira (developed by my team) as the issue creation interface workaround, even for internal users:

• You can share a Smart Form internally (via link, Confluence page, or embedded in a dashboard) with the same conditional logic you use on portal forms.

• Responses map directly to Jira fields and create the issue in the correct project and work item type.

• You can auto-attach the form to the issue so it’s there for future updates — when the user submits the form inside the issue, Jira fields can be updated automatically based on their answers.

• This works like a form-based task template — the form controls which fields are required and ensures they’re filled in before submission.

Example: Select “Bug” and the form shows environment and steps to reproduce; select “Task” and it shows due date and assignee. Submitting it updates the relevant Jira fields without exposing a cluttered static create screen.

That way, you keep dynamic logic, ensure required details are captured

[Sebastian Krzewiński]

Hi @Olha Yevdokymova_SaaSJet ! Thanks! I will review it and check if this fit to my need.

Regards,

Seba