Skip to content

feat(nimbus): add reviewers, editors, jetstream error counts, and conclusion recommendations to reports - #17250

Merged
jaredlockhart merged 3 commits into
mainfrom
17249
Sep 16, 2026
Merged

jaredlockhart merged 3 commits into
mainfrom
17249

Conversation

@jaredlockhart

Copy link
Copy Markdown
Collaborator

Because

  • The CSV and YAML report consumers need to know who reviewed and who edited each experiment
  • Jetstream analysis error counts and the full takeaways set were only visible in the UI

This commit

  • Adds NimbusExperiment convenience properties for reviewer emails, editor emails, and jetstream error counts
  • Adds those fields plus the remaining takeaways fields to the CSV and YAML report serializers
  • Prefetches changelogs with experiment_data deferred on both report querysets

Fixes #17249

…clusion recommendations to reports

Because

* The CSV and YAML report consumers need to know who reviewed and who edited each experiment
* Jetstream analysis error counts and the full takeaways set were only visible in the UI

This commit

* Adds NimbusExperiment convenience properties for reviewer emails, editor emails, and jetstream error counts
* Adds those fields plus the remaining takeaways fields to the CSV and YAML report serializers
* Prefetches changelogs with experiment_data deferred on both report querysets

Fixes #17249
Comment thread docs/experimenter/openapi-schema.json Outdated
"type": "string",
"readOnly": true
},
"jetstream_errors_count": {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small suggestion: it might make sense to name this analysis_errors_count so that it's more self-explanatory, and so it doesn't have to change when we're getting results from highwind.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh good idea

Because

* The report fields should not name the specific analysis backend
* The name will not need to change when results come from highwind

This commit

* Renames the jetstream_errors properties and report fields to analysis_errors

@yashikakhurana yashikakhurana left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

More data, fun, thank you @jaredlockhart

@jaredlockhart
jaredlockhart added this pull request to the merge queue Sep 14, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to no response for status checks Sep 14, 2026
@jaredlockhart
jaredlockhart added this pull request to the merge queue Sep 15, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Sep 15, 2026
@jaredlockhart
jaredlockhart added this pull request to the merge queue Sep 16, 2026
Merged via the queue into main with commit 4a88d4d Sep 16, 2026
32 checks passed
@jaredlockhart
jaredlockhart deleted the 17249 branch September 16, 2026 17:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add reviewer/editor emails, jetstream error counts, and conclusion recommendations to the CSV and YAML reports

3 participants