Change Details

=== Description Test Kitchen UI needs to be updated to include a new CRUD UI that allows some specific users to register/list/modify/remove traffic limit exceptions. To manage a traffic limit exception we will need to consider the following fields: - Experiment name/machine-readable name (both?) - Experiment URI in GrowthBook (something like `https://growthbook.wikimedia.org/experiment/exp_30dhfghfghg`) - Category (`editing`, `account-creation`, `other`) - Traffic (non-standard cases that are not included in any category might need a custom amount of traffic) - This field could be filled automatically based on the category, but saved independently also for standard cases just in case those category values could vary - When the category is `editing`, the traffic value for `enwiki` and other wikis will be 25% - When the category is `account-creation`, the traffic value for `enwiki` and other wikis will be 50% - When the category is `other`, the traffic value can be a specific custom value - Active (something like a checkbox to express whether the traffic limit exception is active or not) === Acceptance criteria [] There is a form via which traffic limit exceptions can be registered [] There is a list view where users can see the active traffic limit exceptions [] There is a way to update an existing traffic limit exception [] There is a way to remove an existing traffic limit exception from the list view

=== Description Test Kitchen UI needs to be updated to include a new CRUD UI that allows some specific users to register/list/modify/remove traffic limit exceptions. To manage a traffic limit exception we will need to consider the following fields: - Experiment name/machine-readable name (both?) - Experiment URI in GrowthBook (something like `https://growthbook.wikimedia.org/experiment/exp_30dhfghfghg`) - Category (`editing`, `account-creation`, `other`) - Traffic (non-standard cases that are not included in any category might need a custom amount of traffic) - This field could be filled automatically based on the category, but saved independently also for standard cases just in case those category values could vary - When the category is `editing`, the traffic value for `enwiki` and other wikis will be 25% - When the category is `account-creation`, the traffic value for `enwiki` and other wikis will be 50% - When the category is `other`, the traffic value can be a specific custom value - When the exception is saved, it becomes active. There should be a button to disable it visible when it's active. === Acceptance criteria [] There is a form via which traffic limit exceptions can be registered [] There is a list view where users can see the active traffic limit exceptions [] There is a way to update an existing traffic limit exception [] There is a way to remove an existing traffic limit exception from the list view

=== Description Test Kitchen UI needs to be updated to include a new CRUD UI that allows some specific users to register/list/modify/remove traffic limit exceptions. To manage a traffic limit exception we will need to consider the following fields: - Experiment name/machine-readable name (both?) - Experiment URI in GrowthBook (something like `https://growthbook.wikimedia.org/experiment/exp_30dhfghfghg`) - Category (`editing`, `account-creation`, `other`) - Traffic (non-standard cases that are not included in any category might need a custom amount of traffic) - This field could be filled automatically based on the category, but saved independently also for standard cases just in case those category values could vary - When the category is `editing`, the traffic value for `enwiki` and other wikis will be 25% - When the category is `account-creation`, the traffic value for `enwiki` and other wikis will be 50% - When the category is `other`, the traffic value can be a specific custom value - Active (something like a checkbox to express whether the traffic limit exception i- When the exception is saved, it becomes active. There should be a button to disable it visible when it's active or not). === Acceptance criteria [] There is a form via which traffic limit exceptions can be registered [] There is a list view where users can see the active traffic limit exceptions [] There is a way to update an existing traffic limit exception [] There is a way to remove an existing traffic limit exception from the list view