Hi everyone - a quick note to say that we have tentatively added this to our roadmap in the next 6-12 months. While we don't have exact dates yet, we understand its importance and will keep you updated on our progress.

Thanks,

Sam

JSM Principal Product Manager

Hi everyone, any updates here? It seems to be a common issue for multiple organizations, June 24 has ended and we are still in the consideration phase?

Hi Eric, just a tip. Have a look at assets as that will likely work for your use case. You can create relationships between assets and it also allows for you to filter subsequent questions based on the entry of an earlier field. https://confluence.atlassian.com/jirakb/how-to-filter-assets-object-within-a-issue-based-on-other-assets-object-custom-field-storing-multiple-objects-in-assets-1142453352.html

Hi, yep, this would be very helpful for us. We want to show custom text fields which would appear when the user chooses an option in a drop-down menu.

This would be very helpful to us as well, as we want to be able to present some fields to the user if a several fields are filled in like If a user is in location A we have a dropdown list of what application access is needed, and another dropdown list for application access when the user is in location B or C. But for all three locations the option Jira Agent is available. It would be nice to make a section appear if Jira agent is selected in the field 'Acceslist location A' or in 'Acceslist location B+C' So for both the same linked Jira field (as you only can link a field once) will be shown where the project can be entered for which they request agent access.

Really want to see this functionality added.

We have a small work around by creating this logic in a linear branches by hiding future questions. It works ok for simple forms and involves duplication of questions content on the form builder (which are not shown to the user) but can quickly get unruly to manage (and you can only show questions one at a time to maintain the logic of the show/hide sections). I'll give a short description of this.

In an ideal world we would make a question that simply evaluates if Q1 OR Q2 are "Yes" - if True this is the complexity needed below to allow us to give different Question content based on those inputs . 

Work around

• Q1) Question 1 Content (Options: Yes; No)
  • NEW SECTION - Show If Q1 is "Yes"
    • Q2.p1) Question 2 Content (Options: Yes; No) 
      • NEW SECTION Section 2.1 Yes - Show if Q2.p1 Yes{}
        • >> Insert any content you want to show if your is "Yes, Yes" (could be more questions etc.) <<
      • NEW SECTION Section 2.1 No - Show if Q2.p1 No
        • >> Insert any content you want to show if your is "Yes, No" (could be more questions etc.) <<
  • NEW SECTION - Show If Q1 is "No"
    • Q2.p2) Question 2 Content (Options: Yes; No) 
      • NEW SECTION Section Q2.2 Yes - Show if Q2.p2 = Yes{}
        • >> Insert any content you want to show if your is "No, Yes" (could be more questions etc.) <<
      • NEW SECTION Section Q2.2 No - Show if Q2.p2 = No
        • >> Insert any content you want to show if your is "No, No" (could be more questions etc.) << 

You can make the rabbit hole as deep as you like.

Gets painful with linked fields (as you see Q2 Content is repeated and we'd need dedicated fields to store each answer, and use automation to unify the responses into a single field on the issue.

This would be amazing, it's so much extra work to build a dedicated form for each request type that needs logic.

From the perspective of a user this seems like a basic feature. Please enable this.

What would be a workaround for OR operator? Example: combine values from 2 fields in 1 field and afterwards use this 1 field.

But I don't like this workaround, because it doesn't look nice from the user perspective.

Any other better workaround?

When it comes to providing a user-friendly and clear portal to the customer, it is necessary to apply logic to the questions that need to be answered. In the meantime, to overcome these limitations, we need to create request types for each possibility.

@Lluis you can use Forms functionality for Jira Service Management Projects and show some fields conditionally only when another previous field will have particular value

When it comes to providing a user-friendly and clear portal to the customer, it is necessary to apply logic to the questions that need to be answered. In the meantime, to overcome these limitations, we need to create request types for each possibility.