We’re guessing that you already have some slick tools for providing great IT support. However, a truly committed service team knows that things could always be better. The simple addition of forms to support requests could be a powerful way to improve your service.
We’re Already Using JSD. Why Do We Need ProForma?
You already have a system for managing and responding to requests for IT support. So why do you need the ProForma app?
Well, lets imagine there are three new requests in your queue; one is to give a new user access to their team’s shared drive, another is for the purchase of new hardware, and the final one is a request for a new Jira custom field. You will need different pieces of information from the requestors in order to fulfill those requests. Some are fairly simple. The person requesting that their new employee be given access to their shared drive, will probably remember to list the name of that employee in the description of their request (but will they remember to tell you what access levels they want the employee to have?).
However, a more complex process like requesting a new custom field will require more information:
- What is the field type?
- Why do you need it?
- What issue types should the new field apply to?
- What are the field properties?
- What screens should the new field appear on?
- How should the field be described to the user?
That’s a lot of information for someone to remember to include in a description. Chances are, they won’t and you’ll go back and forth trying to obtain all the necessary data, dragging out the time to resolution. On the off chance that the requestor does include all of the data needed, you will still lose time parsing that information out of the description field.
Too Much of a Good Thing: Avoiding Custom Field Overload
One way to deal with this is to create custom fields to collect the specific pieces of information needed to fulfill a specific request type. Jira Service Desk certainly makes it possible to do that. But just how many custom fields do you want to manage? We identified six different pieces of key information that needed to be collected in the example above, and that’s just for one request type.
Creating and managing all of the custom fields you’d need could easily become overly burdensome. Furthermore, overuse of custom fields will eventually result in diminished performance.
How Can We Add Forms to JSD?
In the end, their is no better tool for collecting needed information than a form. Forms allow you to:
- Get all of the information you need the first time a request is placed
- Get the information the way you need it (structured and in the most useful field type)
There are several options for integrating forms with Jira. Sadly, many of them involve complex processes and third party integration. ThinkTilt is pleased to offer ProForma, a simple way to create, customize and deploy forms from right within Jira. There’s no need for a third party. No spaghetti plate of custom fields. No going back and forth trying to get all of the information you need.
Chances are, your organization chose to use Jira Service Desk precisely because it provides a simple, efficient and effective way to deliver great customer support. Why not make the most of that wonderful tool by adding ProForma forms?