Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(nimbus): Conclusion recommendations migration #10672

Conversation

yashikakhurana
Copy link
Contributor

Because

  • We want to migrate conclusion recommendation data to a new field to support multi-select

This commit

  • Adds a new migration to get data from conclusion_recommendation to conclusion_recommendations

Fixes #10668

@yashikakhurana
Copy link
Contributor Author

Blocked on #10671

@yashikakhurana yashikakhurana changed the title 10668/conclusion recommendations migration feat(nimbus):Conclusion recommendations migration May 8, 2024
@brennie brennie changed the title feat(nimbus):Conclusion recommendations migration feat(nimbus): Conclusion recommendations migration May 8, 2024
@@ -505,6 +505,7 @@ class NimbusExperimentType(DjangoObjectType):
conclusion_recommendations = graphene.NonNull(
graphene.List(graphene.NonNull(NimbusExperimentConclusionRecommendationEnum))
)

Copy link
Member

Choose a reason for hiding this comment

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

Undo this change

@yashikakhurana yashikakhurana added this pull request to the merge queue May 29, 2024
Merged via the queue into mozilla:main with commit 022c049 May 29, 2024
19 checks passed
@yashikakhurana yashikakhurana deleted the 10668/conclusion_recommendations_migration branch May 29, 2024 18:35
github-merge-queue bot pushed a commit that referenced this pull request May 29, 2024
Because

- We want to use a new conclusion recommendation field that allows user
to select multiple recommendations

This commit

- Add the ability to select multiple (checkbox) for conclusion
recommendations
- Removes field from the summary page to display (radio button)
- Add a new option for `None` as in the old radio button if somebody
selects `None` and saves it, it isn't saving it.
- Rename the conclusion recommendation config
`conclusion_recommendations` option to
`conclusion_recommendations_choices` to avoid name conflict with the new
`conclusion_recommendations` multi-select filed

Note: In the subsequent PR, will migrate the data-
#10672 and remove the field
altogether from frontend and backend

Old UI

<img width="1360" alt="Screenshot 2024-05-28 at 9 11 08 AM"
src="https://github.com/mozilla/experimenter/assets/25848231/edc4de87-ac63-4c0a-abc6-426b30ebfcb5">

New UI
<img width="1360" alt="Screenshot 2024-05-28 at 9 14 35 AM"
src="https://github.com/mozilla/experimenter/assets/25848231/a9ff761d-52b5-429f-935b-211e865e608a">
Multiple badge
<img width="1360" alt="Screenshot 2024-05-29 at 10 00 27 AM"
src="https://github.com/mozilla/experimenter/assets/25848231/4c363ce4-c02d-4acf-bfb4-a551600cfbbe">


Fixes #10671
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.

Migrate radio recommendation data to checkbox data
3 participants