Some ideas explored so far:

• ❌ We could use the work done at T429420: [Customize GrowthBook] Auto-check Pre-Launch Checklist items via the backend poller to add a new automatic step in the poller that marks directly as complete the remaining item
  • Not doable: This non-manual steps only can be checked by GrowthBook. They are hardcoded in the codebase when getting the items of a CheckList, as non-manual steps, and that prevent the specific endpoint from being able to checked via the API. It's explicitly noted in the related API endpoint in their docs: https://docs.growthbook.io/api/#tag/experiments/operation/postExperimentStartChecklistManualComplete where it's said that (auto-computed items cannot be updated via this endpoint)

• ❌ Also via T429420: [Customize GrowthBook] Auto-check Pre-Launch Checklist items via the backend poller, we could use the validation process to make, via API request, the manual configuration step that the remaining item requires. That way GrowthBook would check the item as done automatically pretty soon
  • Not doable. Probably because the above, the endpoints that are available to modify experiments don't allow to modify those properties (they seem to be hardcoded while getting Checklist items). A fully manual human step is required

• ❌ Because those three items are hardcoded in the codebase, we could create a fork, update it and build our own docker image as usual but based on that. But I assume that, at least for now, we don't want to do that

• 🕐 After asking GrowthBook team for this, they filed a ticket in GitHub to add a way to hide/disable those items somehow
  • We assume this approach, if considered, will take time

• Document somewhere, at least for now, that experiment owners can ignore that item and "Start Anyway" the experiment when needed
  • Not nice because it introduces some noise for users who need to review the full Checklist, but it seems that, for now, it seems it is what we can do

Any other ideas?

Document somewhere, at least for now, that experiment owners can ignore that item and "Start Anyway" the experiment when needed
Not nice because it introduces some noise for users who need to review the full Checklist, but it seems that, for now, it seems it is what we can do

It does seem like this is our only option right now. I think this is ok, as long as it's clear in documentation and in any onboarding videos we create. I'll continue to press GrowthBook for a change on their side.