How to speed up Jira performance with bundled custom fields
Working with Jira Software Server issues or Jira Service Desk Server requests, often there is a situation when you need to provide small chunks of information as parts of a greater whole. Then you have to create a massive amount of custom fields to store this information and keep it structured, which can slow down the software significantly. Fortunately, this won’t be the case anymore if you upgrade your Dynamic Forms for Jira or Extension for Jira Service Desk to the latest version. We proudly present Bundled Fields, which allow you to store multiple pieces of information in a single custom field! It is then displayed on screens as an additional form, which you can update at any moment. In this article, we‘ll explain when and how to use the new feature.
First look at Bundled Fields
Custom fields in Jira Service Desk
If someone purchases a laptop from you on behalf of their company, they need to provide two addresses in the request: for shipping and for billing. These two do not always match in case of a big organization, and also you may often store different parts of customers’ addresses in different fields to search through the database faster. This is where Bundled Fields – a feature available in Extension for Jira Service Desk – come in handy. Instead of having a separate custom fields for every city, street, zip code or whatever, you can bundle them all as a whole. To customize the fields’ display further, you can set up the Show Label option or change fields’ size and location.
Bundled Fields can be also useful within your organization. Let’s say, you work in technical support and receive bug reports from different departments. Your colleagues want to report an issue related to one of the apps they work with. Using custom fields in Jira, they provide you with information about the application’s version, their problem’s first occurrence and steps already taken. This way you can easily understand the issue and replicate it.
What’s more, you can search for information stored inside Bundled Fields as easily as you do with any other field in Jira! To do so, go to Issues → Search for issues. With our dedicated Bundled Fields Searcher, you have two search methods to use in JQL – with two arguments and with three arguments.
- Syntax with two arguments
issue in bundledFieldsEx(“customfield_name”, “subfield_value”)
issue in bundledFieldsEx(“customfield_id”, “subfield_value”)
- Syntax with three arguments
issue in bundledFieldsEx(“customfield_name”, “subfield_name”, “subfield_value”)
issue in bundledFieldsEx(“customfield_id”, “subfield_name”, “subfield_value”)
Taking as an example task TS-14 and choosing three arguments option, we can create a syntax – issue in bundledFieldsEx(“Problem in the app”, “Star App’s version”, “version 2.0”). Note that in case of the custom field name, you should use a system name of a chosen field. Display name of your custom field won’t work in JQL.
Custom fields in Jira Software
Quite unexpectedly, even though the feature was originally designed for Jira Service Desk, you can also use it in your Jira Software. It is because we included Bundled Fields in Dynamic Forms for Jira application. How to take advantage of it?
Let’s say you work in the HR department and you’re responsible for organizing workspaces for new employees in several departments. Instead of creating a long description of the new tools that they need, you can bundle some information in one place. This way you’ll make the task view clearer. Details and Description will be also easier to read for your colleagues from the technical support department which is in charge of providing hardware, software and small electronic devices.
As in Extension for Jira Service Desk, in Dynamic Forms for Jira, you can also search for details kept inside Bundled Fields. Our dedicated Bundled Fields Searcher works the same way here. The only difference is that instead of
issue in bundledFieldsEx, you’ll write
issue in bundledFieldsDF– the rest of the syntax works the same.
Bundled custom fields configuration
The first step is to add a Bundled Field to Jira and assign it to the screens where you want to display it. Even though this field type is delivered exclusively by the app, you still do it in the Custom fields settings. Note that you can quickly proceed there by clicking the plus icon in the Bundled Fields configuration. Obviously, you can have more than one Bundled Field set-up for different purposes, but keep in mind that each of them must be added to Jira separately. Also, remember to add it to the appropriate request types, if you plan on using the feature in Jira Service Desk.
After that, come back to the configuration and set up the fields you’ve created. You can choose the alignment of the field’s display (horizontal or vertical). Then provide the rows of fields to bundle and make some of them required, if you need it. Once you’re all set, save the setup. From now on, your users will fill in this form when creating a Jira issue or a helpdesk request.
If you need to modify your Bundled Fields layout, there’s a way to do that. The option Turn on Edit mode, which you can see in Layout settings, allows you to change fields’ size and location. Note that in order to have your modified layout both on Create Issue and View Issue screen, you need to select Layout in the Alignment field. Below you can see where exactly to find this feature and how it looks in action.
So, do you see how easily you can clean up the database of your Jira Software Server or Jira Service Desk Server with Bundled Fields? With this feature, you store more information in a smaller amount of fields while retaining its searchability. This way you’ll never get lost and you’ll improve your Jira performance. Additionally, you can customize your Bundled Fields layout so that your issue view will look clearer.
If you’d like to learn more about Dynamic Forms for Jira or Extension for Jira Service Desk, take a free 30-day trial from the Atlassian Marketplace. If you’d like to see the app in action, book a live demo via Calendly. You can also read more on the subject:
Also published on the Atlassian Community.