Prompt

Why can’t our search find old Jira tickets and Confluence pages?

Technology / Search & Discovery Tools1 observationLast seen Oct 13, 2026

Latest observation

Oct 13, 2026OpenAI APIWeb search: off

There are a few common reasons this happens in Jira/Confluence, and most of them come down to search indexing, permissions, or retention:

1) The content may not be indexed anymore

  • Old tickets/pages can disappear from search if the index is incomplete, stale, or corrupted.
  • If you recently migrated, changed servers, or restored from backup, the search index may not include everything.

2) Permissions can hide results

  • Jira/Confluence search only returns content you’re allowed to see.
  • If old tickets/pages were moved to a project or space with tighter permissions, they won’t show up in your search.

3) The content may have been archived or deleted

  • Jira issues can be archived, moved, or deleted.
  • Confluence pages/spaces can be archived or removed, which makes them harder or impossible to find via normal search.

4) Search filters may be excluding older content

  • Date filters, project/space filters, text matching rules, or default “relevance” behavior can hide older items.
  • In Confluence especially, search may prefer recent or highly relevant pages unless you search by exact terms.

5) The query might not match the stored text

  • Titles changed over time.
  • Ticket keys/pages may be referenced differently than you expect.
  • Content in attachments, comments, or page bodies may not be fully searchable depending on configuration.

6) Indexing jobs may be delayed or broken

  • If background indexing is failing, new or old content might not appear consistently.
  • This is especially common after upgrades or on large instances.

7) There may be app/platform limitations

  • If you’re using Atlassian Cloud, some results behavior differs from Data Center/Server.
  • If you’re searching through another tool that integrates with Jira/Confluence, its connector may only sync part of the history.

Quick checks

  • Search by exact issue key or page title.
  • Check permissions on the project/space.
  • Look for archived spaces/projects/pages.
  • Verify whether search works in the native Jira/Confluence UI.
  • Ask an admin to check the search index status/logs.

If you want, I can help you narrow it down with a quick checklist based on whether you’re on Jira/Confluence Cloud or Data Center, and whether the missing items are tickets, pages, or both.

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (1 observation for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as dotdotPR. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.