Unfortunately, I was not completely correct. Clicking the blue message box still executes a search, so it does not really offer speed improvements, just a bit more clarity about the fact that refreshing the screen (i.e. clicking the message) will show new fields for searching.

We will use JRA-5484 to track the improvement of this.

It is possible to search on project or issue type specific fields without doing a search first since JIRA 3.5.

You will need to make a selection of one or more projects and/or issue types. When you do that, a blue information message will appear informing you that if you click the message you will see more fields: e.g. versions and components (if only one project is selected) and relevant custom fields. If you click the message the page will refresh and you will see new fields.

It is still not possible to search on context specific custom fields on the first Issue Navigator screen, without selecting project and/or issue type and refreshing the page. I will leave JRA-5484 to track that improvement.

Implemeting JRA-5484 will resolve Ingomar's process/speed issue.

Implementing JRA-9692 will resolve this issue.

Please reopen, I have the same request from our users. The process search->select issue type->fillin search field->do search is reported as being to lengthy for our use.

If you select the Issue Type and the search the Custom Field should then appear in the Search Form.
Custom Fields during searching are context sensative so Issue Type fields only appear when searching their Issue Type and the same for projects.