About 6 months ago, I was moving a legacy ticketing system to JIRA. In addition to importing the old data, I also needed to synchronise not the JIRA issue data, but the actual options displayed in the drop down lists on the Create Issue screen.
I was planning to write my own plugin to do this, but just before I began I thought ‘lets have one more look in the user created JIRA plugin library first’. By some amazing luck, a new plugin had been added in the last few months that did exactly what I required: Wim Deblauwe’s Database Values plugin.
This plugin allows you to connect to an external database, fetch some values, and use them to populate the options in your custom fields.
We are using it in several ways, the most useful of which is to display our product model range in our JIRA. When a user reports a problem with a product, then can select the product from a huge cascading drop down list (a 2 level drop down list containing Product Category/Model). This prevents any ambiguity and reduces chance of user error. It also allows us to standardise searches for specific models across multiple JIRA projects.
The list of models comes from a legacy system. The added bonus of this is that when we later export the JIRA issue data to that legacy system, the drop down list values are the same so the data can be exported as is without any filter program in between. The plugin retains not only the values (e.g. “Product XYZ”) but also any key associated with it (e.g. “018”).
I presume it would also be possible to connect to an MS Outlook address book in order to display customer names. This is something I may need to set up in future as we start to use JIRA for more CRM related activity.
You can also sort the values however you wish using an SQL query. Another cool feature is that it can display the values using the JIRA AJAX textbox. See Database Values for further information on this great plugin.