We have a JIRA project with submission form that uses cascading select fields. They change based on the option chosen and this is configured with the help of groovy scripts inside JIRA.
Now, when I try to create a Jira issue collector for that project, it allows to add all those custom fields, however completely breaking the logic I configured with groovy.
How can I use Jira Issue collector and leave the logic of cascading fields unchanged?
Say I have a field "Will you join the conference?":
- Yes
- No
If "No" is selected, then another fields appears: "Please explain the reason".
This logic works greatly if used directly from JIRA. However when used from the issue collector, I only have option to make all the fields available in the form so it looks like below:
---------------------------------
"Will you join the conference?"
- Yes
- No
Please explain the reason"
---------------------------------
How do I save that "if this than that" logic using the JIRA Issue collector? Thanks!
Although not strictly related to Groovy and Jira Issue collector, a (possibly simpler) solution for the problem of changing fields based on the values entered in previous fields can be found in our add-on ProForma.
There is a Dynamic Fields feature which will dynamically show or hide form sections based on values entered into previous fields.
If you would like to give it a go for free you can evaluate by installing ProForma Lite
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.