Description
- When creating a new experiment, the project field pre‑selects:
- A project the user doesn’t usually work in, or
- A generic or deprecated project.
- Users must manually change it each time, leading to errors when they forget.
Solution
- Review defaulting rules:
- Katalyst may default to the last used project, a system default, or a user’s primary project.
- Adjust configuration:
- If there is a global default project, set it to a commonly used, generic project if that fits your policy.
- If supported, set user‑specific defaults (e.g., each user’s main project).
- User practice:
- Train users to double‑check the project selection on experiment creation.
- For important projects, consider requiring project selection (no silent default).
- For mis‑assigned experiments:
- Correct project values in the affected experiments, either manually or via admin scripts, to avoid reporting inconsistencies.
Comments
0 comments
Article is closed for comments.