Wouldn’t it be nice if you could have your cake and eat it too? Imagine having all of the detailed information you need (structured so it’s easy to find) on a Jira issue without having to create custom fields.
Embedding a form, or several forms, in a Jira issue, is the solution. Forms are an enduring business tool because they make it easy to get the precise, detailed data that’s required for a particular process. The information can be structured, formatted and validated to meet your teams’ needs.
While forms can be created for any possible use case (see the ProForma template library for examples), it’s helpful to consider the broad ways that forms can make Jira even more effective.
Forms can be used to preserve and display the thinking behind the decision to carry out a particular project. This is useful for Project Initiation Documents, use cases, KPIs and business justifications. Simply put, it allows you to keep the answer to the question, “Why are we doing this?” in front of the team members who are working on a project. This serves to keep everyone motivated and limit scope creep.
Creating a new product? There are a lot of features that need to be specified. Forms let you break out all of that information into individual fields so it can be easily inputted, viewed and addressed. There’s no risk of missing important details that are lumped together in the description field. ProForma includes the option of locking the form, so that the contents cannot be changed once the form has been submitted.
Forms are the right way to get the required information for processing service requests. If customers are not prompted with specific questions, they may forget to include important details when creating a request. This means that the agent will need to go back and ask for the information. The customer gets frustrated by the delay and work in progress piles up for the service agent. Things would have been better for everyone if all of the information had been provided in the first place. In fact, a well-designed request form can be the key to providing one-touch service.
If you’re using Jira Service Desk, the ProForma library of process templates makes it easy to bring services into Jira. Each template includes a portal form, request type, workflow and any needed secondary forms, all in one install.
Forms can also be used to create that mother of all tracking tools – the checklist. Including a checklist on an issue means you can standardize procedures and limit the use of sub-tasks. Whether the checklist represents acceptance criteria, a definition of done, or an ongoing to do list – you can include as many items as needed and organize them into logical sections for easy navigation. Multiple checklists can be added to a single issue and you can include comment fields for times when checklist items need a little more explanation.
ProForma Custom Forms & Fields for Jira
Fields that are added to forms are fields that don’t need to be added to the Jira issues themselves. For items that you need to query or report on, you can link form data to a Jira field with one simple click. This means fewer issue types, fewer custom fields and better Jira performance. Thus, the ProForma app makes Jira more manageable, as well as more useful.