For Administrators - Search Attachments

Indexing


The plugin needs an index to perform the search. When you attach files to JIRA issues, they are indexed automatically, but the previously-existing attachments have to be indexed by hand:

  • Open JIRA and go to the plugin configuration page (Administration > Add-ons > Manage add-ons > Search Attachments Configure)
  • Click Reindex
  • Click Back to configuration;
  • Wait for Indexing in progress message to disappear. If you have many issues and attachments, it can take even a few hours to complete.


Until you'll do full reindex after installation, the plugin may find only some attachments, or even no attachments. You will also see incomplete search results when the reindexing is in progress. 

Advanced settings for indexing

This feature is available in 1.5.6 plugin version and later.

Plugin during indexing creates some files to save information required to search attachment. Default directory for this is placed:

JIRA Home Directory/caches/indexes/attachments

To change this place you sholud:

  • Open JIRA and go to the plugin configuration page (Administration > Add-ons > Manage add-ons > Search Attachments Configure)
  • Check field Custom in Path to index directory section
  • Enter correct path to Path field
  • Click Save changes button

After change path you must reindex attachments.

To free up disk space you should delete old index directory.

Attachment exclusion

This feature is available in 1.7.0 plugin version or later.


Attachments can be excluded from indexing using 3 kind of rules:

  • File name wildcard e.g. *.jar
  • File size greater than [MB] e.g. 100
  • Project key e.g. DEMO

If more than one rule is added there is logical alternative between them ex. file name matches *.jar or file size is greater than 100 MB

After exclusion configuration you must reindex attachments.

Skipping large files from indexing

This feature is available in 1.7.0 plugin version or later.

If there is not enough memory while indexing files larger than 100MB additional logs can occur in log file:

There is no enough memory to index file={} of size={}, free memory={}

In that case consider extending maximum heap size for your instance by changing jvm -Xmx parameter.