Custom Fields - Nested questions

[Melorie Acevedo]

Hello:

Could you please let me know if you have or plan to be able to take custom fields and add nested questions?  

For example, our PI Planning has a field for impacted teams and business units. We want a secondary drop-down list for each impacted team to show the effort each team puts into the project, IE (Testing only, discovery, defect resolution, development).

Has anyone encountered this situation, and how did you address it? 

[Nick Haller]

Hi @Melorie Acevedo ,

Not entirely sure I understand the ask here, or what you might be referring to as "nested questions."

Are the efforts (Testing only, discovery, defect resolution, development) the nested questions?

Are you hoping that when the impacted team / business unit field is selected, a "child" field then appears related to the selected value - which are the nested questions?

Does Jira or another Atlassian product currently offer anything similar you can share that may help understand the ask?

[Melorie Acevedo]

Hello @Nick Haller

Thank you for your clarifying question. Yes, we have multiple development teams that an idea from a different development-owning team may impact. We want a child field (thus nested) or a sub-dropdown so that each impacted team has a level of effort. 

For example, Idea JP-123 - Build a guest checkout, owned by the online team, has an impacted team of TechDev with a sub-dropdown of development work, whereas the other impacted team, Order Management, has testing-only work.

[Nick Haller]

Hi @Melorie Acevedo ,

Thank you for clarifying. JPD does not really offer something like this currently within a field. But I do think the closest thing would be deliveries.

Having said that, it might only work if each impacted team has their own Jira project, or if all teams manage their issues within the same Jira project.

Regardless, an idea can have multiple linked delivery tickets through different Jira projects, and all linked deliveries can be monitored through both the Delivery Progress and Delivery Status fields:

In the example above, the Delivery Progress field is configured to count all issues under each delivery - so also accounting the child issues of each delivery. Not sure if that helps, but maybe will be somewhat a decent workaround. Let us know what you think.

[Hermance NDounga]

Hello Melorie, 

Jira Product Discovery does not support cascading fields - that's how they are called in Jira. 

However, based on the example you gave, I believe you could easily regroup all the different values under one field and let users pick among the 4 values that are proposed.

However if your exemple is "complete" (like, there is really just one sub option per team), I think you can actually simply skip this field and fill it automatically! automation. 

My suggestion: 

• Create two fields 
  • Field 1: Team= Tech Dev, Order Management ...
  • Field 2: Effort = Testing only, development work ...
• On your form, only display Field 1. 
• In automation set a rule as follows: 
  - WHEN an idea is created
  - IF Field 1 = Tech Dev
  - THEN Field 2 = development work 
  - IF Field 1 = Order Management 
  - THEN Field 2 = Testing only 
  and so on and so forth. 

If you want to learn more about automations, you can check this automation guide 

Best Regards,
Hermance
Product Manager @ Jira Product Discovery