Issue Summary

The space picker search UI — used in both Confluence Automation rule builder and page editor macros (e.g. Content Tree, Page Tree) — returns zero results whenever the user's search input ends with the letter "s".

This affects all space picker UIs that rely on the shared SpaceSelectorQuery / space search component. The issue is reproducible across multiple tenants (production and sandbox), with both English and Japanese space titles, and is not limited to Confluence Automation.

The suspected root cause is English stemming / pluralisation logic in the search query pipeline. When the input ends with "s", the query builder appears to strip or transform it (treating it as a plural suffix), which causes the prefix/exact match against the indexed space title to fail.

This also explains a previously reported Japanese-language issue: when the Japanese tokeniser (Kuromoji) completes a token (e.g. 質問), it appears to trigger a similar query processing path, causing the match to fail in the same way.

Additional Findings (March 2026)

The issue scope appears to be wider than the initial trailing "s" hypothesis:

Some inputs ending with "s" still return results, so the failure is not uniform for all trailing-"s" searches.
Multibyte + ASCII mixed input can also fail, for example: 第2 → ❌.
Hiragana input can fail from the 2nd character onward, for example: ひ → ✅, ひら → ❌.
Additional customer observations indicate similar failures may also occur with other multibyte-leading inputs. Behaviour may vary by tenant and input pattern.
/wiki/spaces directory search is not affected. The issue appears to be isolated to the shared space picker component used by Automation builder and macro configuration UIs.
These findings suggest the issue is broader than English stemming logic alone and may involve how the space picker query is processed for certain inputs.

Steps to Reproduce

1. In a Confluence Cloud site, ensure a space exists whose title ends with the letter "s" (e.g. a space named "Documents").
2. Open one of the following UIs:
   • Automation rule builder → Add a "Copy page" (or "Move page" / "Publish new page") action → Click the "Space" field.
   • Page editor → Insert a macro that has a space picker (e.g. Content Tree) → Click the space selection field.
3. Type characters one by one and observe the dropdown:
   • Type D → matching spaces appear in the dropdown ✅
   • Type Do → matching spaces appear ✅
   • Type Doc → matching spaces appear ✅
   • Type Documen → matching spaces appear ✅
   • Type Document → matching spaces appear ✅
   • Type Documents → dropdown shows "No options" / zero results ❌
   • Type Documents  (add a trailing half-width space) → matching spaces appear again ✅
4. Repeat with other inputs to confirm the pattern is tied to trailing "s":
   • Atlassian → ✅ hit
   • Atlassians → ❌ no hit
   • Atlassiana → ✅ hit (control test: non-"s" ending)
   • Report → ✅ hit
   • Reports → ❌ no hit
5. (Optional) Reproduce with a Japanese space title (e.g. 質問):
   • 質 → ✅ hit
   • 質問 → ❌ no hit
   • 質問  (trailing half-width space) → ✅ hit

Expected Results

The space picker dropdown should continue to display matching spaces regardless of whether the search input ends with the letter "s". Typing Documents should match a space titled "Documents", just as typing Document does.

Actual Results

When the search input ends with the letter "s", the space picker dropdown returns zero results ("No options"). The matching space that was visible one character earlier (e.g. at Document) disappears entirely from the dropdown.

Adding a trailing half-width space after the "s" (e.g. {{Documents }}) restores the expected search results.

This behaviour occurs in:

• Confluence Automation rule builder (Space field in Copy page, Move page, Publish new page, etc.)

• Page editor macros with a space picker (e.g. Content Tree, Page Tree)

• Multiple tenants (both production and sandbox instances)

• Both English and Japanese space titles

No exception was observed in the browser console. The issue appears to be in the search query construction / processing layer rather than a client-side error.

Workaround

The following workarounds are available until the bug is fixed:

1. Type up to the character before "s" and select from the dropdown:
   For example, to find the space "Documents", type Document and select the matching space from the dropdown list.
2. Add a trailing half-width space after "s":
   If the above produces too many candidates, type the full name including "s" and then add one half-width space at the end (e.g. Documents ). This restores normal search results.
3. For Japanese space titles:
   Type only the first character (e.g. 質 instead of 質問) and select from the dropdown, or add a trailing half-width space after the full title.