Search indexing
System administration
- Finding your Server ID
- Increasing Jira application memory
- Using the database integrity checker
- Precompiling JSP pages
- Logging and profiling
- Backing up data
- Restoring data
- Search indexing
- Using robots.txt to hide from search engines
- Control anonymous user access
- Moderating user group activity with Safeguards
- Licensing your Jira applications
- Viewing your system information
- Monitor application performance
- Monitoring database connection usage
- Monitor your instance with Jira diagnostics plugin
- Viewing Jira application instrumentation statistics
- Generating a thread dump
- Finding your Jira application Support Entitlement Number (SEN)
- Auditing in Jira
- Monitor security threats
- Data pipeline
- Important directories and files
- Integrating Jira applications with a Web server
- Securing Jira applications with Apache HTTP Server
- Changing Jira application TCP ports
- Connecting to SSL services
- Running Jira applications over SSL or HTTPS
- Configuring security in the external environment
- Data collection policy
- Jira Admin Helper
- Raising support requests as an administrator
- Start and Stop Jira applications
- Managing LexoRank
- Jira cluster monitoring
- Scheduler administration
- Secured secrets by default
On this page
In this section
Related content
- No related content found
To provide fast searching, Jira creates an index of the text entered into issue fields. This index is either stored on the file system when using Lucene, or in an OpenSearch cluster and updated whenever issue text is added or modified. It's sometimes necessary to regenerate the index manually. For example, when you add a new custom field, or if the index is lost or corrupted. For more information on when you should re-index, check Re-indexing after major configuration changes.
Read more:
Last modified on Sep 8, 2025
In this section
Related content
- No related content found
Powered by Confluence and Scroll Viewport.