When it comes to raising a service desk request, time and details count. However, users value the simplicity of the request forms, which they don’t always get. Especially when it comes to issues that require in-depth details, “simple” isn’t the word that describes the form. Such requests usually mean plenty of ‘important’ fields to fill, making the questionnaire longish and over-detailed, which in turn makes it hard to tell which questions are really important and which we can skip. That also relates to Jira Service Desk where default request forms are static. To make simplicity and detailed go together in terms of its request forms, we can turn to apps like Extension for Jira Service Desk featuring Dynamic Forms which provide a quantum boost for Jira Service Desk user experience.
Just like filling in the request form shouldn’t be that complicated, setting up Dynamic Forms is also quite easy. We only need to:
For example, we have a Hardware field where the user can choose if they want to order a laptop, monitor or something else. To the laptop option, we link the Operating system field. There, we relate Brand and Screen resolution fields with Windows option. This way, each time a user wants to order a laptop, the question about the operating system will show up. And once they choose Windows, the form will extend by additional questions about a laptop brand and screen resolution.
Extension for Jira Service Desk is available on Cloud instances as well. The Cloud version of the app also involves only a 3-step setup of Dynamic Forms, though it’s slightly different from the Server one because we need to define validators and conditions for the fields instead of choosing a master field and assigning related fields to the options.
Frequently, we receive questions about the difference between Dynamic Forms featured in Extension for Jira Service Desk and our other app, Dynamic Forms for Jira. In both cases, the aim is the same – improving the user’s experience with Jira Service Desk and Jira respectively. And even though Dynamic Forms for Jira is based on the Extension app feature, there are more differences than similarities.
Starting with the most obvious one, the Extension app is dedicated to Jira Service Desk, while Dynamic Forms is for Jira Software. Also, there’s a Cloud version of the former.
Then we have fields supported by the apps. To build a dynamic request form, we use two kinds of fields: master and related fields. The former is the main dynamic field with various options to choose from. The latter one is the one we link to a specific option of the master field so that when the user chooses this option, the appropriate field will show up, expanding the form. Dynamic Forms for Jira and Extension for Jira Service Desk vary when it comes to what kind of fields we can use for either master or related fields. When it comes to master fields:
As for the related fields:
Another major difference is that Dynamic Forms for Jira provides visualization of the field relations as well as tooltips and required validation messages with translations for related fields.
Even though Dynamic Forms are quite different depending on the app, they still serve one purpose – to make the experience as seamless and trouble-free as possible for the customers. This means that they will spend less time and fewer nerves figuring out which fields they should focus on because the appropriate ones will show up according to their answers. By adding dynamic fields to the request form, we replace longish and over-detailed forms with the top-down ones.
Read more about Dynamic Forms for Jira Software and Service Desk:
Dzmitry Hryb _Deviniti_Marketplace Partner
This month the spotlight is on AppLiger. We caught up with Pavel Pavlovsky, CEO and Product Manager, to learn how the company started and what fuels the team's creativity. Atlassian:...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events