From 7efd30696973b13e60308ba74c902b48256ad4a4 Mon Sep 17 00:00:00 2001 From: Thomas Heartman Date: Fri, 18 Mar 2022 14:28:06 +0100 Subject: [PATCH] docs: link to strategy constraints from the schedule how-to guide --- website/docs/how-to/how-to-schedule-feature-releases.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/how-to/how-to-schedule-feature-releases.mdx b/website/docs/how-to/how-to-schedule-feature-releases.mdx index eed3a00b94e..b5d7ac9645b 100644 --- a/website/docs/how-to/how-to-schedule-feature-releases.mdx +++ b/website/docs/how-to/how-to-schedule-feature-releases.mdx @@ -27,7 +27,7 @@ This guide assumes that you've got the following: ## Schedule feature releases with strategy constraints {#strategy-constraints} -You can use this approach with _any_ strategy you want. The strategies will work just as they normally do, they just won't become active until the specified time. For example: with the standard strategy, the feature would become available to all your users at the specified time; with a gradual rollout, the rollout would start at the specified time. +[Strategy contstraints](../advanced/strategy-constraints.md#date-and-time-operators) are the easiest way to schedule feature releases. You can use this approach with _any_ strategy you want. The strategies will work just as they normally do, they just won't become active until the specified time. For example: with the standard strategy, the feature would become available to all your users at the specified time; with a gradual rollout, the rollout would start at the specified time. ### Step 1: Add an activation strategy with a date-based constraint