RFCs are a way for Atlassian to share what we’re working on with our valued developer community.
It’s a document for building shared understanding of a topic. It expresses a technical solution, but can also communicate how it should be built or even document standards. The most important aspect of an RFC is that a written specification facilitates feedback and drives consensus. It is not a tool for approving or committing to ideas, but more so a collaborative practice to shape an idea and to find serious flaws early.
Please respect our community guidelines: keep it welcoming and safe by commenting on the idea not the people (especially the author); keep it tidy by keeping on topic; empower the community by keeping comments constructive. Thanks!
Summary
Rovo Search gives Atlassian users AI-enhanced search across Jira, Confluence and connected third-party tools. Today, Forge apps can’t use it. This RFC proposes a new Forge API, requestRovoSearch(), that lets apps run Rovo Search from their backend, together with knowledge sources: an admin control that decides which content an app is allowed to search.
Rovo Search is generally superior to regular JQL/CQL keyword search because it returns semantic+keyword results with cross-product ML-based ranking. This means results better match the intent of the query.
-
Publish: 13 Nov 2026
-
Discuss: 27 Nov 2026
-
Resolve: 11 Dec 2026
Problem
Many Forge apps need to find relevant content before they can do something useful: enrich a ticket, detect a duplicate, route a request or provide context for an agent. Today, developers have to:
-
Call product-specific search APIs (for example, JQL and CQL) one at a time and merge the results themselves.
-
Build their own relevance ranking on top of keyword search.
-
Can’t search content from third-party sources that customers have connected to Rovo.
Proposal
-
A new
requestRovoSearch()function in the Forge API, available from resolvers and other backend functions, which runs a single cross-product Rovo Search query and returns ranked results. -
A new
read:knowledge:rovoscope that an app must declare in its manifest to use Rovo Search. -
Knowledge sources for Forge apps: site admins choose which sources (for example, specific Confluence spaces, Jira projects or connected third-party tools) an installed app can search. This builds on the same knowledge source experience customers already use for Rovo Studio agents.
API shape
Request
const { results, errors, totalCount, nextCursor, hasMore } = await api.asUser().requestRovoSearch({
query: "Q3 roadmap planning",
first: 10,
after: null, // pass nextCursor from previous response to paginate
entities: [ //optional: defaults to all available
"confluence:page",
"confluence:blogpost",
"slack:message",
],
filters: { //Strong typing to make query building easy
commonFilters: {
range: {
lastModified: {
gt: "2026-07-04T00:00:00Z",
},
},
},
jiraFilters: {
projects: ['PROJ']
}
},
});
Response
{
errors: null,
results: [
{
title: "Q3 Roadmap Planning — Ecosystem",
url: "https://abc.atlassian.net/wiki/spaces/ECO/pages/123456",
snippet: "This page outlines key deliverables for Q3...",
type: "confluence:page",
id: "ari:cloud:confluence:<cloudId>:page/10234",
},
{
title: "PROJ-669 – E2E test ownership restructure",
url: "https://abc.atlassian.net/browse/PROJ-669",
snippet: "Tracks the change in ownership model for ful...",
type: "jira:issue",
id: "ari:cloud:jira:<cloudId>:issue/10234",
},
{
title: "John Smith in #proj-abc",
url: "https://abc.enterprise.slack.com/archives/C0AQ83C5YD9/p17888...",
text: "Here's an update about our roadmap planning for Q3...",
type: "slack:message",
id: "ari:cloud:graph::message/activation/a436116f-…/3e8a24ab-…",
}
],
totalCount: 47,
nextCursor: "eyJvZmZzZXQiOjEwfQ==",
hasMore: true,
}
Each result includes either text or snippet:
-
text: the full content of the item, in plain text. It’s returned when the full content is available from search (e.g. slack:message). -
snippet: an excerpt relevant to the query, for items whose full content isn’t returned (e.g. confluence:page, jira:issue). To get the full content, call the relevant API with the ID.
Partial results and errors
Because one query searches several products, a failure in one product doesn’t fail the whole request. For example, if the caller can’t search Confluence, you still get Jira results:
{
results: [
{
title: "PROJ-669 – E2E test ownership restructure",
url: "https://product-fabric.atlassian.net/browse/PROJ-669",
snippet: "Tracks the change in ownership model for ful...",
type: "jira:issue",
id: "ari:cloud:jira:<cloudId>:issue/10234",
},
],
errors: [
{
message: "Caller is not authorized to search Confluence",
statusCode: 403,
product: "confluence",
integration: null,
},
],
totalCount: 17,
nextCursor: null,
hasMore: false,
}
Manifest
permissions:
scopes:
- read:knowledge:rovo
Knowledge sources and permissions
An app can only search content that passes all of these checks:
-
Scope: the app declares
read:knowledge:rovoin its manifest. -
Knowledge sources: a site admin has selected the sources the app may search. By default, an app has no knowledge sources until an admin enables them.
-
Request: the sources and entity types the app asks for in
requestRovoSearch(). -
Content permissions: existing per-item permissions still apply. For example, a user who can see one Jira work item but not another only gets results for the one they can see.
In other words, the sources an app searches are:
admin-selected knowledge sources ∩ sources requested in the API call ∩ sources visible to user
Admins will configure knowledge sources from the app’s admin settings, using the same source picker that’s used for Rovo Studio agents today.
asUser and asApp
requestRovoSearch() supports both asUser() and asApp().
-
asUser()searches with the permissions of the user who invoked the app. Use this wherever there’s a signed-in user. -
asApp()searches with the app’s own permissions. This is needed for modules that run without a signed-in user, such as scheduled triggers, event triggers, web triggers and Jira workflow post functions. In this case, restricted pages can not be searched.
Example use cases
Example 1: Ticket enrichment
A Jira Service Management app runs when a request is created, searches Confluence for related runbooks and known issues, and adds links to the request so agents can resolve it faster.
Example 2: Duplicate detection
A Jira app runs when a work item is created, searches for similar open work items in the same project and flags likely duplicates.
Example 3: Cross-product knowledge for Forge Rovo agents
A Forge app exposes an action that calls requestRovoSearch() to find relevant pages and work items. Forge Rovo agents can use this action to answer questions using the customer’s own content, including connected third-party tools.
Asks
-
Use cases: What would you build first, and for which customers? Which entity types and third-party sources matter most? Would you use
asUseror requireasApp? -
API shape: Does the request and response shape fit how you’d use search? What fields or filters are missing (for example, author, space, project, labels or content body)?
-
Knowledge sources: Does admin-selected knowledge sources, defaulting to none, work for your customers? How would you explain the setup step to admins during onboarding?
How to give feedback
-
Comment directly on this RFC thread in the Atlassian Developer Community.
-
Share use cases, concerns and suggestions to help shape Rovo Search for Forge.
