Use statuses

You can assign a status to each split when creating or updating targeting rules. Statuses provide a way for teams to indicate which stage of a release or rollout a feature is in at any given moment, and as a way for teammates to filter their splits to see only features in a particular stage of the internal release process.

Note: For more information about the rollout board, refer to the Use the Rollout board guide.

Change the status of a split

When you review the Change summary page for saving or submitting a change for a split definition, you can change a particular status of your split. To change a status, do the following:

1. After submitting a change to the rollout plan of a split, on the Change summary page, in the Status field, select the desired status, e.g. Internal testing.

   Note: If you create a new split, the default is Pre-production. For any existing split, it keeps its existing status.

2. After you make a selection, click Confirm.

If you want to change the status of that split without changing the rollout plan, you can mark a split as permanent or removed from the code, or to assign a status if you forgot to do so when you changed your targeting rules. To change the status, do the following:

1. From the main Split screen, select the split you want to assign a new status to.

2. On the upper right hand corner, select the status field down arrow.

3. Select the desired status. A change status message appears asking if you want to change the status.

4. Click Confirm.

Display and filter your statuses

Once you assign statuses to your splits, you can then display and filter them to view the ones within the browse area that are relevant to you. To display and filter your splits, do the following:

1. On the left hand navigation bar, click Splits. A list of splits and their associated status badges display.

2. From the Splits view, select Filter and then Status. The list of filters displays.

3. Select the desired statuses that you want to view. The selected statuses display in the browse area.

Status definitions

The following explains the available statuses:

• Pre-Production (grey). Indicates splits where code for the feature isn’t pushed to production.

• 0% in Production (grey). Indicates splits where code for the feature is pushed to prod but not turned on for anyone

• Killed (red). Indicates splits that are moved to the default treatment due to an issue or bug

• Internal Testing (blue). Indicates splits that have only been turned on for users that are employees or contractors

• External Beta (blue). Indicates splits that have been turned on for a few external beta customers that have been pre-selected or chosen for early access to a feature

• Ramping (blue). Indicates splits that are turned on for a small percentage of users to make sure no performance issues or larger issues come up

• Experimenting (blue). Indicates splits that have are ramped for max power in an experiment to get results as quickly as possible

• 100% Released (green). Indicates splits that have been moved to be fully on for all customers

• Removed from Code (white). Indicates splits that have been removed from the codebase

• Permanent (white). Indicates splits that are set to be permanent circuit breakers in the application