Issue Summary

“Team“ and "Parent Link" fields are not available via aggregation in both searchStream() or search() when using the field ID (customfield_xxxxx) or the field name. 

Steps to Reproduce

1. Try get aggregated Teams data is via CountAggregation or TermsAggregation parameters, which call the searchStream() or search(), using the Field ID (customfield_xxxxx) or Field Name.

Expected Results

The team and Parent Link fields are indexed with doc values, and is available via aggregation in both searchStream() or search()

Actual Results

The Team index field is registered twice by two different Atlassian components (team-management-plugin and team-management-customfields module) with incompatible index settings: one registers it as stored but without doc values, the other with doc values but not stored. The conflict is resolved by whichever registers last, with only a warning logged, so the outcome depends on plugin startup order. Because neither registration provides both settings, Team can never be both retrievable and aggregatable at the same time.

  "error": "Can't aggregate on 'customfield_11800' because the field does not exist. Make sure this field is indexed with the new 'com.atlassian.jira.search.issue.index.indexers.FieldIndexer'",

Workaround

• Both fields, "Team" and "Parent Link", are available for aggregation in the search API using the index physical name:
  • "ISSUEPROP_jpo-issue-properties$team_id".
  • "ISSUEPROP_jpo-issue-properties$parent_id"

Additional Notes

• None of the metric aggregations (including ValueCountAggregation) are available for this field as it's a keyword, and numeric aggregation require a numeric. All the BucketAggregation are available though (this includes TermsAggregation)
• This was not introduced in Jira 11. In prior Jira versions, developers needed to use the physical index field name when working with a Lucene Collector.