Admin Guide

This guide explains how Jira administrators can configure Recall, choose which projects to enable, and understand how Recall behaves in day-to-day usage.

Recall is designed to be simple to operate, with sensible defaults and minimal ongoing administration.

Who should use this guide

You should read this guide if you are:

• A Jira administrator installing Recall
• A project admin enabling Recall for specific projects
• An engineering manager responsible for Jira hygiene and issue quality

Installing Recall

Recall is installed from the Atlassian Marketplace like any other Jira Cloud app.

During installation:

• Required Jira permissions are displayed
• No configuration is required to complete installation

After installation, Recall is inactive until projects are explicitly enabled.

Enabling projects

Project-based configuration

Recall operates only on Jira projects that are explicitly enabled by an administrator.

This allows you to:

• Control which data is indexed
• Start small and expand gradually
• Exclude sensitive or irrelevant projects

How to enable a project

1. Open Jira Apps → Recall → Administration
2. Select Enabled Projects
3. Choose one or more Jira projects
4. Save changes

Recall will begin indexing issues for newly enabled projects automatically.

Initial indexing behavior

What happens during indexing

• Existing issues in enabled projects are indexed
• Indexing runs in the background
• Jira users can continue working normally

Indexing duration

Indexing time depends on:

• Number of issues
• Issue size and history

Typical behavior:

• Small projects: minutes
• Medium projects: tens of minutes
• Large projects: background indexing over longer periods

Recall becomes usable before indexing is fully complete.

Ongoing updates

Recall automatically keeps its index up to date.

The following events trigger updates:

• Issue creation
• Issue edits
• New comments
• Status or resolution changes

No manual reindexing is required in normal operation.

How Recall searches work (high level)

When a user views or creates an issue:

• Recall searches for similar issues
• Results may include open or resolved issues
• Results are ranked by relevance

Recall uses multiple internal techniques to provide accurate results. The exact ranking behavior is managed automatically.

Performance and reliability

Recall is designed to:

• Scale with project size
• Adapt to usage patterns automatically
• Automatically shift to a faster, simpler ranking mode during periods of very high demand, so suggestions keep appearing even if the more advanced ranking step is temporarily skipped

Administrators do not need to tune performance settings.

Plans and project limits

Recall plans define how many projects can be enabled and how many issues can be indexed in total across those projects:

If you reach your project limit:

• Additional projects cannot be enabled
• Existing projects continue to work normally

If you reach your indexed-issues limit:

• Indexing pauses once your plan's total is reached
• Already-indexed issues remain fully searchable — nothing is removed
• The enabled-projects list shows a notice that the cap has been reached, with options to upgrade or contact us

Data handling overview

Recall processes Jira issue data only for enabled projects.

At a high level:

• Issue summaries and descriptions are processed
• Portions of comments may be used for relevance
• Data is used only to provide Recall functionality

Detailed data handling and security information is available in our Privacy Policy.

Troubleshooting & FAQs

Recall does not show results

• Verify the project is enabled
• Allow time for initial indexing
• Check that issues exist in the project

Recall results seem incomplete

• Confirm all relevant projects are enabled
• Newly updated issues may take a short time to reindex

Recall is slow

• Temporary delays may occur during high activity
• Recall automatically adjusts to maintain stability

When to contact support

Contact support if:

• Indexing does not progress after an extended period
• You need to enable more projects than your plan allows
• Your organization has special compliance or performance requirements

Enterprise options are available for advanced needs.

Summary

• Recall is configured per project
• Minimal administration is required
• Indexing and updates are automatic
• Performance and reliability are handled internally
• Project and indexed-issue limits are enforced per plan

This design keeps Recall simple, predictable, and easy to operate.