This is the fifth article in our series on Form Design. Previous articles covered Why Form Design Matters, Form Layout and Flow, writing Good Form Questions - Open Questions and Good Form Questions Part 2 - Choice and Conditional Logic.
The first time I converted a paper form to an online form, I made my online form a perfect replica of its predecessor. I figured the team I was building the form for would appreciate my being faithful to their original and I wanted them to feel reassured that the transition to digital did not mean they had to abandon their processes.
Later I learned that there are several reasons you shouldn't do that:
Instead of copying, gather the stakeholders and start from a blank slate. There are several things you should consider before creating your form:
Now you’re ready to create you screen/form. Remember to:
Try to use other options such as a ProForma field, a field configuration, or a field context.
By engaging in a careful discovery process and employing the rules of good form design, you can help teams maximize usability and efficiency as they bring their processes into Jira.
I hope you’ve found this series on form design helpful. From here, we’ll be turning it over to our friend and Jira super-user, Rachel Wright, who will tell us about how to implement these strategies on your Jira screens.
Previous article in the series
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