I am proud to announce a new 1.1 version of the JIRA Database Values Plugin. It has the following improvements:
- Support AJAX lookup in searching: If you use the simple mode for searching in JIRA, you can now select a value from your custom field via AJAX lookup. This makes it a lot easier then that long list of items you might have in the default search mode. The only drawback is that you can only select 1 item. The list allows multi-selection. Use the
search.typeproperty in your configuration file to select with search mode you want to use.
- Support for history and activity view: You can now choose how your value is rendered in the history view and the activity views. In previous versions, the primary key was displayed, which is usually not what you want. Use
rendering.changelog.viewpatternin the configuration file to configure this. Note that it is optional as the
rendering.viewpatternwill be used by default.
- Support for statistics views: You can now use your custom field in a pie chart, 2d statistics filter and single level group by report. If you want to set a different rendering pattern for these views, use the
rendering.statistics.viewpatternkey in your properties file. Note that this one does not support HTML, so if your
rendering.viewpatternhas HTML, you need to add this key and provide a pattern that does not use HTML.
- Choose how to render NULL values: Previous releases of the plugin always rendered a NULL value as ‘Unknown’. As of this release, it will be rendered as an empty string. You can override what is shown by using this:
This means that a null value in the 2nd column of your SQL query will be rendered as ‘N/A’. Thanks to Andrew Gallagher for providing the patch.
- Add a separate query for the search: You might want to separate the queries you use for editing/viewing and searching. The property
sql.query.searchkey allows to do just this.
This version was tested with the latest JIRA version, which is 4.1.2 at the time of writing.
Go download it from the plugin exchange and try it out!