Change Details

=== Description As part of the validation process that was implemented already, the poller could check if any specific requirement related to a Checklist item is met already, and mark it as checked via GrowthBook API, by making a request to `/api/v1/experiments/<experiment-id>/start-checklist/manual/complete`. Similarly this new feature could uncheck any item when their related requirements are not met. Hopefully, an experiment owner would have their Pre-Launch Checklist automatically checked if the experiment was registered properly. Otherwise, the remaining items would be there just like a reminder that there is something wrong that needs to be fixed. And once fixed, the poller would check those ones again automatically. === Acceptance criteria [] The backend poller marks a Pre-Launch Checklist items as checked when their related requirements are met [] The backend poller marks a Pre-Launch Checklist items as unchecked when their related requirements aren't met

=== Description As part of the validation process that was implemented already, the poller could check if any specific requirement related to a Checklist item is met already, and mark it as checked via GrowthBook API, by making a request to `/api/v1/experiments/<experiment-id>/start-checklist/manual/complete`. Similarly this new feature could uncheck any item when their related requirements are not met. Hopefully, an experiment owner would have their Pre-Launch Checklist automatically checked if the experiment was registered properly. Otherwise, the remaining items would be there just like a reminder that there is something wrong that needs to be fixed. And once fixed, the poller would check those ones again automatically. === Acceptance criteria [] The backend poller marks a Pre-Launch Checklist items as checked when their related requirements are met [] ~~The backend poller marks a Pre-Launch Checklist items as unchecked when their related requirements aren't met~~ (not doable. There is only endpoints to either see the current status of a Checklist or set its items as complete. There is nothing about reverting the status of an item in a Checklist)

=== Description As part of the validation process that was implemented already, the poller could check if any specific requirement related to a Checklist item is met already, and mark it as checked via GrowthBook API, by making a request to `/api/v1/experiments/<experiment-id>/start-checklist/manual/complete`. Similarly this new feature could uncheck any item when their related requirements are not met. Hopefully, an experiment owner would have their Pre-Launch Checklist automatically checked if the experiment was registered properly. Otherwise, the remaining items would be there just like a reminder that there is something wrong that needs to be fixed. And once fixed, the poller would check those ones again automatically. === Acceptance criteria [] The backend poller marks a Pre-Launch Checklist items as checked when their related requirements are met [] ~~The backend poller marks a Pre-Launch Checklist items as unchecked when their related requirements aren't met~~ (not doable. There is only endpoints to either see the current status of a Checklist or set its items as complete. There is nothing about reverting the status of an item in a Checklist)