Adding a "meta issue" template

[CEHENKLE]

Description

During the 3/31 OpenSearch triage, we noticed that we had several meta issues that didn't have enough details for someone who wasn't working on the project to understand what was trying to be accomplished.

This template attempts to capture the conversation around "goodness" of a meta ticket here: https://opensearch.slack.com/archives/C05L60S4UBT/p1706720978192339

Related Issues

No related issue

Check List

• New functionality includes testing.
• All tests pass
• New functionality has been documented.
• New functionality has javadoc added
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[peternied]

@CEHENKLE Thanks for building this up - give us a baseline quality on our meta issues that will be easy for the community to engage with and if we do see meta issues that can be improved, this is a straight forward way to improve an existing issue by recreating it with this template.

[github-actions]

Compatibility status:

Checks if related components are compatible with change a7d64d5

Incompatible components

Skipped components

Compatible components

Compatible components: [https://github.com/opensearch-project/custom-codecs.git, https://github.com/opensearch-project/observability.git, https://github.com/opensearch-project/flow-framework.git, https://github.com/opensearch-project/cross-cluster-replication.git, https://github.com/opensearch-project/job-scheduler.git, https://github.com/opensearch-project/geospatial.git, https://github.com/opensearch-project/opensearch-oci-object-storage.git, https://github.com/opensearch-project/sql.git, https://github.com/opensearch-project/neural-search.git, https://github.com/opensearch-project/asynchronous-search.git, https://github.com/opensearch-project/k-nn.git, https://github.com/opensearch-project/reporting.git, https://github.com/opensearch-project/security-analytics.git, https://github.com/opensearch-project/ml-commons.git, https://github.com/opensearch-project/notifications.git, https://github.com/opensearch-project/common-utils.git, https://github.com/opensearch-project/performance-analyzer-rca.git, https://github.com/opensearch-project/index-management.git, https://github.com/opensearch-project/anomaly-detection.git, https://github.com/opensearch-project/security.git, https://github.com/opensearch-project/alerting.git, https://github.com/opensearch-project/performance-analyzer.git]

[github-actions]

✅ Gradle check result for fcd3bf4: SUCCESS

[peternied]

@CEHENKLE Looks like you had some changes that aren't signed off with the DCO, can you updated these?

[CEHENKLE]

@CEHENKLE Looks like you had some changes that aren't signed off with the DCO, can you updated these?

D'oh! I'll fix it Monday, thanks :)

[github-actions]

❌ Gradle check result for 5f3da48: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[kartg]

Gradle check failure is from known flaky test #9191

> Task :server:internalClusterTest

Tests with failures:
 - org.opensearch.remotestore.RemoteIndexPrimaryRelocationIT.testPrimaryRelocationWhileIndexing

4576 tests completed, 1 failed, 44 skipped
...

[github-actions]

❌ Gradle check result for 5f3da48:

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 5f3da48: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❕ Gradle check result for a7d64d5: UNSTABLE

• TEST FAILURES:

      1 org.opensearch.search.SearchWeightedRoutingIT.testMultiGetWithNetworkDisruption_FailOpenEnabled

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[codecov]

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (445bf1f) 71.36% compared to head (a7d64d5) 71.46%.
Report is 1 commits behind head on main.

Files	Patch %	Lines
.../org/opensearch/telemetry/tracing/SpanBuilder.java	95.23%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #12148      +/-   ##
============================================
+ Coverage     71.36%   71.46%   +0.09%     
- Complexity    59643    59700      +57     
============================================
  Files          4954     4954              
  Lines        280695   280712      +17     
  Branches      40780    40783       +3     
============================================
+ Hits         200319   200608     +289     
+ Misses        63688    63448     -240     
+ Partials      16688    16656      -32     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.