Feature Request: Time-Based Rollout Strategy Templates

[luismafra]

Is your feature request related to a problem? Please describe.

Yes. Currently, FeatureHub supports reusable rollout strategies, but they are shared across all features that use them. This means that any modification to a strategy affects the behavior of all flags using it simultaneously.
For example, I might want to roll out Flag A starting at 10:00 AM and Flag B starting at 10:05 AM using the same strategy template, but currently there's no way to do this without the flags interfering with each other or having to manually duplicate and manage multiple identical strategies.

Describe the solution you'd like

I'd like to have Rollout Strategy Templates that act as blueprints for time-based progressive rollouts. When a template is applied to a feature flag, it should create an independent instance of that strategy for that specific flag.

Example workflow:

1. Create a reusable strategy template: "Progressive 20-minute rollout"

   • Starts at 0%
   • Progressively increases: 10% → 20% → 30% → ... → 100%
   • Total duration: 20 minutes
   • Targets different accounts/user segments at each step

2. Apply this template to Flag A at 10:00 AM

   • Flag A starts its independent rollout: 10:00 AM (0%) → 10:20 AM (100%)

3. Apply the same template to Flag B at 10:05 AM

   • Flag B starts its own independent rollout: 10:05 AM (0%) → 10:25 AM (100%)

Each flag would have its own:

• Start time (when the strategy was applied)
• Current state/progress
• Target completion time
• Ability to pause/resume/cancel/rollback independently

Describe alternatives you've considered

1. Using current percentage rollout manually - Manually adjust the percentage over time for each flag, but this defeats the purpose of automation and is error-prone.

2. External orchestration - Use the FeatureHub API to programmatically update rollout strategy of flags over time from an external service, but this adds complexity, requires additional infrastructure, and moves the rollout logic outside of FeatureHub.

Additional context

This feature would enable progressive delivery patterns, but specifically for feature flags.

Benefits:

• Consistency: Same rollout pattern across multiple flags
• Independence: Each flag rolls out on its own timeline
• Safety: Gradual rollout reduces blast radius
• Flexibility: Apply proven rollout patterns at different times
• Reusability: Define once, use many times

This would be particularly useful for teams doing continuous delivery with multiple feature flags that need to roll out safely but independently.