How to make certain fields required based on values in prior fields

Question

I'm trying to setup a request where a customer gets present with different fields, based on a value they've set in a previous field.  Ex.  First field set is "application".  That is a LOV with values like "Finance", "HR", "Projects"  etc.

User select "Finance", then they get presented with a bunch of fields related to Finance like "Accounting Period", "Set of Books".

Whereas if user select "HR", they might get fields to enter like "Employee Name", "Job", "Termination Date".

An if user selects "Projects", they might get fields like "Project Number", "Customer", "Description".

Is there a way to do this on JIRA Cloud?

jesusoros · Answer

Hey Jeremy,

For the situation you mention about having related options based on an answer, you could take a look at the Select List (cascading) Custom Field, so you can provide different options to the selected root, for example:

The Custom Field "Is this related to a non-conformance?" (mandatory) with Yes: Options "Dev", "QA", etc with No: Option: No

Yet if I understand correctly, you want fields to appear and like I mentioned before, that is not a functionality that JIRA has, every screen you see is loaded from a template and the information is analyzed by JIRA until you click on "Finish".

Please let me know if this helped.

Jeremy Steuhl · Answer

Thanks Jesus.  I was thinking different projects/request types would be a workaround for this.  I wasn't sure if there was a good add-on out there that anyone might recommend.

I was also thinking that certain fields might be required within a issue based on a value set in a prior field.  For example, a field might be "Is this related to a non-conformance?", with Yes/No values.  If user select Yes, then a new field "list non-conformances" might appear and be required, where as if the user selects No, the new field would either not show or be optional.

jesusoros · Answer

Hi Jeremy,

What you are trying to accomplish is not very recommended on an Administrator point of view; because unfortunately the Fields shown when you create an Issue are defaulted since you select the Issue Type and it's not dynamic.

On this kind of request I suggest you to create different Issue Types based on your example:

-Issue type "Finance", they get presented with a bunch of fields related to Finance like "Accounting Period", "Set of Books".

-Issue type "HR", they might get fields to enter like "Employee Name", "Job", "Termination Date".

That would be the best setup for your project. As far as the experience that I have, a lot of Teams prefer to have a Project created for every Team, and on its Issue Types they add the services that team provides.

Please let me know if this helps, or if you have something else in mind that would push you towards looking for this kind of setup.

Thanks!