Hi community.
I need to create a dynamic form.
for example.
I have a radio button field with yes and no options.
if the select option is "no". then the create button should be disabled and a message should be displayed in the screen
anyone knows a workarround to resolve it?
thanks in advance.
best regards.
Hi @Sergio Palacio,
@Calvin Senteza is right if it comes to the exact case you described, provided that only native Jira Service Desk configuration is used. But there is no possibility to set up dynamic fields that way, which can be done with Extension for Jira Service Desk. With the app, creating dynamic request forms is a simple 3-step process. Read this article of mine to learn the details: https://community.atlassian.com/t5/Marketplace-Apps-articles/3-Simple-Steps-to-Set-Up-Dynamic-Forms-in-Jira/ba-p/822317
The best way I can think of to fix this issue is to add two things. A validator to the workflow being used, and editing the description field in the request type of the project.
First you'll want to edit your workflow, specifically the transition from the ticket being created to the first status that it enters. Click on that transition and click on the option labeled Validators. Within the new screen click on the option labeled "Add Validator" From here click on the radio button labeled "Regular expression check" and click "add". On the following page choose the name of the drop down custom field you want to verify and select it. for the regular expression field fill it in with the exact case sensitive name of the radio button you want to be selected in order for the ticket to be created. In your case I assume that would be "yes". Click "add" again and make sure to publish the workflow. It is always a good idea to opt to keep a copy fo the workflow during the publishing process in case you need to roll it back. If you have multiple workflows for the project and want them all to require the yes radio button on ticket creation you will need to make this change in all of them.
Now your best option if you were to make this an internal change would be to use a message field of some sort but at this time message fields are not currently supported by the JIRA Customer portal as they are part of an add-on. In it's stay I recommend you include a description on your yes/no custom field. Make sure to edit this through the project settings. Head to the Request Types section and add a description to the yes or no fields within the request types that utilize it and the workflow that verifies the field. The description should state that in order for a user to progress through the ticket they will need to select the "yes" field or whatever field you decide to specify in the workflow. Keep in mind in Cloud this functionality only adds a "i" icon that the user will have to click to see the info however on server this should create a small paragraph to the side of the field. Effectively making a "Notification" for the user so that they are aware of how to proceed. be sure to test out this functionality itself to make sure it's working.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.