Scroll to top
en pl

How to Speed Up Jira with Bundled Fields

Krzysztof Skoropada - 9 March 2018 - 0 comments

How to Speed Up Jira with Bundled Fields

Working with issues in Jira, often there is a situation when users 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. But 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 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.


Jira Service Desk

If someone purchases a laptop from you on behalf of their company, they need to provide two addresses: for shipping and for billing. These two do not always match in case of a big organisation, 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 come in handy – instead of having a separate custom field for every city, street, zip code or whatever, you can bundle them all as a whole. What’s more, you can search for information stored inside a Bundled Field as easily as you do with any other field in Jira! To customize the field’s display further, you can set up the Show Label option. On the screenshot below, it is turned off, but the field is still easily recognizable.

Bundled Fields in Jira Service Desk

If you’d like to learn more on how to set up and use Bundled Fields in Jira Service Desk, watch this video.


Jira Software

Quite unexpectedly, even though the feature was designed originally for Jira Service Desk, you can also use it as a lightweight test management tool! In Jira Software, your developers can store the test steps for a feature in a Bundled Field. That’s right – you never have the exact same amount of steps when you test things, so you need to edit them frequently. But here comes the Dynamic Configuration option, which allows users to add new rows during filling in the form. This way it becomes flexible and tailored to what you want to do.

Bundled Fields in Jira Software


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 add a hint to help users fill in the form, choose the alignment of the field’s display (horizontal or vertical), and turn the abovementioned Dynamic Configuration option on or off. Then provide the rows of fields to bundle and make some of them required, if you need it. You’ll see how a Bundled Field looks like with these settings at the bottom of the configuration screen.

Then save the setup. From now on, your users will fill in this form when creating an issue or a helpdesk request.

Bundled Fields Configuration


So, do you see how easily you can clean up the database of your Jira with Bundled Fields? With them, you store more information in a smaller amount of fields while retaining its searchability. This way you never get lost and improve your Jira’s performance just by using it.

If you’d like to learn more about Dynamic Forms for Jira Service Desk, take a free 30-day trial from the Atlassian Marketplace. You can also book a live demo via Calendly, if you’d like to see the app in action, or read more on the subject:

Also published on the Atlassian Community.

Related posts