Targeting a segment (not include)

[paulwer]

Describe the feature request

We would therefore like to request this functionality, to allow us to not target a segment in a gradual rollout.

Background

Hello everyone,
for security reasons we have a flag, which is called OTP_DISABLED.
Therefore when its true, it will be omited (in front & backend).
To be prone to situations, where the flag cannot be fetched, we descided to go this way.

We now wanted to use one of our segments and redisable this feature again for those, so they start testing using otp again.

We are able to define a NOT IN rule for userIds / organizationIds, but we are not able to NOT include a segment within a Rollout.

Solution suggestions

add a NOT toogle to the segment selection + add support on the server

[chriswk]

We don't currently support this, as a workaround you can make the inverse of the segment as a new segment and make a new strategy using this segment instead.

[paulwer]

Hi,
thaks for your response. As of we are using this segment for some organizatioIds, the inverse would be several tousand, which is not aplicable. For now we have added the organizations with the not operator without using our segment.

We would be very happy, if this could be added as a feature in the future.

Thank you.

[chriswk]

Hi @paulwer . It's a great idea, and we will add it to our backlog, which means it probably won't happen in the coming month, but it will happen