Team-managed project bug: parent = <EPIC> returns nothing unless ORDER BY parent is added

[Mohamed Hazem]

In a Team-managed Jira Software Cloud project,
JQL `parent = KEY-1` returns no results,
but `parent = KEY-1 ORDER BY parent` returns all child issues.

Both issues are valid (Epic → Task). The “Parent” field is visible in the child issue,
and the Timeline view shows them correctly. This started after a CSV import.

Environment:
- Jira Cloud Free
- Team-managed project
- No access to reindex functionality

Expected:
`parent = KEY-1` should return the same issues as with ORDER BY clause.

Actual:
`parent = KEY-1` returns nothing, `parent = KEY-1 ORDER BY parent` returns correct issues.

This looks like a partial index update problem (similar to JRACLOUD-81933).

Can an Atlassian engineer please force a reindex or suggest a workaround?

Thanks a lot in advance!

[Jayesh]

Hello @Mohamed Hazem 

It seems you hit the issue https://jira.atlassian.com/browse/JRACLOUD-81933 

The workaround is mentioned if you want you can try.

Thanks
Jayesh R

[Christos Markoulatos]

Hey  @Mohamed Hazem 

This looks like a Cloud indexing quirk after the CSV import. You’re using the right JQL (parent = KEY-1 is the current, unified field for epic/parent in Cloud), but you can’t trigger a manual re‑index on Cloud, Atlassian handles it automatically.

What to try now

• Self‑heal via bulk edit: Run the query that does return results (parent = KEY-1 ORDER BY parent), bulk‑edit those issues, and make a no‑op change (e.g., add a temporary label, then remove it). This forces those items to be re‑indexed individually on Cloud.
• Touch the Parent field once: For a couple of children, clear Parent, re‑add the epic, re‑check the plain parent = KEY-1 search. If that fixes it, repeat via bulk change (or a short automation).
• If CSV was involved: There are known CSV issues in Team‑managed projects that can disturb parent/epic links; review your mapping and consider a small re‑import test mapped to the Parent field (issue IDs), or rebuild parents via bulk edit/automation.

Notes

• Cloud sites don’t expose a “reindex” button; indexing runs automatically. For stubborn cases after CSV, Atlassian Support can investigate, but on Free plan tooling is limited, bulk edits are the fastest workaround.

Docs

• ‘Epic Link’ → Parent change (use parent = …) [support.at...assian.com]
• Cloud: re‑indexing isn’t user‑triggered [community....assian.com]
• CSV + Team‑managed: parent/epic bugs & workaround

Hope this helps!

[Mohamed Hazem]

Thanks for the ideas @Christos Markoulatos

Unfortunately, the only thing that worked in the end was to bulk move the epics (and their children) to a different project, then moving them back.