You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an Experiment is created from the Feature's experiment rule, the assignment table of the corresponding experiment is silently non-configured. This confuses users. Observed up to the build aa0207f.
Expected Behavior
When an Experiment is created from the Feature's experiment rule, then either of both applies:
The assignment table is selected correctly according to the rule's assignment attribute.
The user gets informed that the experiment assignment table needs to be set consistently by hand.
Current Behavior
When an Experiment is created from the Feature's experiment rule, the assignment table of the corresponding experiment is silently non-configured.
The Analysis Settings from the experiment look like this:
A click on the button "Update" shows the following error
This might be the expected behaviour. However, it feels like a bug, since it's first noticeable when the error in the latter screenshot is shown.
The text was updated successfully, but these errors were encountered:
Summary
When an Experiment is created from the Feature's experiment rule, the assignment table of the corresponding experiment is silently non-configured. This confuses users. Observed up to the build aa0207f.
Expected Behavior
When an Experiment is created from the Feature's experiment rule, then either of both applies:
Current Behavior
When an Experiment is created from the Feature's experiment rule, the assignment table of the corresponding experiment is silently non-configured.
The Analysis Settings from the experiment look like this:
![image](https://private-user-images.githubusercontent.com/30110352/303381720-2a032cdc-b099-4e2b-b455-0a0550da21d5.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTg4ODM3NTMsIm5iZiI6MTcxODg4MzQ1MywicGF0aCI6Ii8zMDExMDM1Mi8zMDMzODE3MjAtMmEwMzJjZGMtYjA5OS00ZTJiLWI0NTUtMGEwNTUwZGEyMWQ1LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MjAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjIwVDExMzczM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTJhMTZhZDIwNTdhMmE5ZmZlZThkMGQwMDM0NjZmMGY5OTU5NmEyOTdiNDU0MTc2YWE2ZWNhNDJmNTllOGJmNjYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.Bq-OILYNNt4d14V6gywowCojFYdPq2LZEOAlGz6hTwQ)
A click on the button "Update" shows the following error
![image](https://private-user-images.githubusercontent.com/30110352/303382901-aa328590-7559-45f3-a8eb-db5b1a871be0.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTg4ODM3NTMsIm5iZiI6MTcxODg4MzQ1MywicGF0aCI6Ii8zMDExMDM1Mi8zMDMzODI5MDEtYWEzMjg1OTAtNzU1OS00NWYzLWE4ZWItZGI1YjFhODcxYmUwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MjAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjIwVDExMzczM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWRjMjZiYTM1NWU1YTlhODRjNjc5ZTIwZTMwOTk1OTA2NzNjNDViNDk3NWU5MGNiNmNiYzM1OTAwNTg1ZjYyOTAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.chLO9MAd_4iO2Hw7-YM_8QGoDk0lhItRDh6EE-1CXX4)
This might be the expected behaviour. However, it feels like a bug, since it's first noticeable when the error in the latter screenshot is shown.
The text was updated successfully, but these errors were encountered: