Documentation for JIRA 5.2. Documentation for other versions of JIRA is available too. 
![]()
In order to provide fast searching, JIRA creates an index of the text entered into issue fields. This index is stored on the file system, and updated whenever issue text is added or modified. It is sometimes necessary to regenerate this index manually; for instance if issues have been manually entered into the database, or the index has been lost or corrupted.
See Re-Indexing after Major Configuration Changes for more information on when you should re-index.
This page allows you to:
スクリーンショット: JIRA のインデックス再作成
The Re-index all issues option should be used in the majority of circumstances, particularly following changes to the configuration. It will generally take significantly longer to perform than the Delete and rebuild all indices option, but it allows JIRA to remain usable while it is being done. There will however be a performance impact on JIRA as a whole. We recommend that you perform this option during a low usage period. The actual impact of running the Re-index all issues option will depend upon the customer's particular hardware and software installation as well as how many issues are in the system.
The Delete and rebuild all indexes should be used when:
The following table summarises the differences between the two options:
| Re-index all issues | Delete and rebuild all indexes |
|---|---|
| 完了まで時間がかかります。 | 比較的早く完了 (最大 2 倍速い場合もあります)。 |
ユーザーはインデックス再作成中も JIRA を使用できます。 | JIRA cannot be used by users during re-index. |
| Can be cancelled at any time. | Cannot be cancelled once started. |
caches/indexes subdirectory of the JIRA Home Directory.