Any tips for configuring complex submission forms?

[Andrew Zimmerman]

I'm working with  my office's administrative team to revamp the create screen for a request type they have in their Service Desk project.

However, their request for the renewed intake form is pretty complex. They're hoping for lots of itemized data points they want in separate fields. Currently, there is just a tip message, describing what details a user should enter into a multi-line text field (it's just the Description field). However, the team has told me this isn't working, and users submitting these requests have not been fully filling out those description details as described in the tip message. 

The team has also told me they definitely need answers to all these questions/data points, in order to accurately complete the request. Hence their desire to itemize each question into different fields and make them all required.

Furthermore, they're requesting a lot of dynamic logic. They don't want certain fields to appear until previous fields are answered, and they want to change requirement/validation logic based on how previous questions on the form are answered. In short, they want to build a creation process that is more like a Google Forms, step-by-step submission, rather than a Jira "create screen."

As an admin, I am not willing to add 30+ custom fields to meet this request, as we already have too many fields in our instance and this is the only project in which these fields would likely ever be used. We also have Deviniti Dynamic Forms, so I can configure pieces of the dynamic logic and bundled fields this team is requesting, but not to the scale and complexity they desire.

So, I'm looking for a middle ground here. I don't want to turn the team away from Jira because this is how they track their admin work, but they need so many details from users to properly take action on this request type, that I'm not sure how to set this up without making either an atrocious user experience or putting our instance in a bad spot administratively (fielditis).

Any tips and ideas are welcome. App recommendations are welcome too, but I'm really hoping to solve this using tools we already have in our stack.

Thanks!

Andrew

[Yann]

Hi Andrew,

Thanks so much for your question.

There is, unfortunately, nothing out of the box in Atlassian right now, but you can search for market place apps that can help you achieve what you need:

https://marketplace.atlassian.com/search?hosting=server&product=jira-service-desk&query=dynamic form service desk

Thank you,

Yann
Jira Service Desk