Skip to end of banner
Go to start of banner

Search Issues

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

Before performing an issue search based on a database custom field value, you must set a search template for that custom field. To do so, follow the steps described in the Searcher section of the Configuration user guide.

After a searcher has been set for the database custom field, you can perform a search for all issues containing the desired value for that custom field.

For a detailed explanation on searching issues in JIRA, you can check the Searching for Issues tutorial from the JIRA documentation.

Search operation can be performed based on main database custom fields, as well as on child database custom fields.

Basically, to perform an issue search based on a database custom field value, you will use the Issue Navigator:

Custom fields can be searched, as you can see in the bottom part of the navigator panel, but note that they will only appear in the search form on the left when appropriate. That is:

  • Custom fields that relate to a particular project will only appear in the search form after you choose that project.
  • Custom fields that relate to a particular issue type will only appear in the search form after you choose that issue type.

After introducing the desired value to search for in the database custom field (as simple text value), and selecting any other needed filters, press the search button.

All issues containing the searched value for that database custom field will be displayed in the right part of the search panel, as it is shown in the screenshot above.

Jira 4.4.x only

There is a known issue when installing this plugin via UPM: the database custom fields won't be displayed on the search screen of JIRA.

This is caused by a known JIRA bug: https://jira.atlassian.com/browse/JRA-25284 and will probably be resolved in future JIRA releases.

So far the workaround to resolve this issue temporarily without restarting JIRA is to go to the Custom Field admin screen, click Edit for any of the custom fields provided by the plugin, then save the field without making any changes.

You can also use one of the two alternative methods for installing Database Custom field Installation via Kepler Installer or Manual Install.

  • No labels