Hi!
For example i ve got this case:
Question1
Question2
If someone has selected option A1 in Question1, then set the answer to A2 in Question2 and prevent Question2 any changes from being made.
If someone choose B1/C1 then in Q2 all options are possible.
Alternatively, do you know of any workarounds :P
Hola Tomasz,
@Viswanathan Ramachandran’s suggestions are the main options, but there’s an important difference between them.
Native Jira Forms can conditionally show or hide questions based on an earlier answer. They can’t currently, however, set Question 2 to A2 automatically and make that answer read-only while the user is completing the form. Jira Automation runs after the form or work item is submitted so that it can correct the stored value afterward, but it won’t dynamically lock Question 2 on the open form.
A native workaround would be a cascading select field. Configure A1 so its only child option is A2, while B1 and C1 each allow A2, B2, and C2. That correctly limits the available answers, although the user may still need to select A2 rather than have it automatically chosen. Atlassian explains cascading fields here.
Another Forms-only workaround is to place Question 2 in conditional sections. When A1 is selected, show text stating that A2 will be used and hide the editable Question 2 field. When B1 or C1 is selected, show the normal Question 2 field. You could then link the form questions to Jira fields and, after submission, use automation to set Question 2 to A2 for the A1 path. Conditional sections are described here.
If you need the value to change immediately and become genuinely read-only on the form, you’ll need an app that supports field behaviors, such as ScriptRunner Behaviors or a similar dynamic-forms app.
Thanks,
James
I've done this with Assets in the past as well! Though this may be overcomplicating the solution depending on your use case and goals.
Create object fields for List 1 and List 2, and use AQL (Assets Query Language) in the child field filters to show specific options. Figured it would be worth a share just in case!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you have script runner, you could use Behaviours.
Or you could achieve this using Native cascading select and Jira Automation.
See this video and hopefully it helps Automation & Cascading Select
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.