Summary
Please add an option to configure custom result states at the project level, instead of only organization-wide.
Current behaviour
Today, custom result states are defined once and apply to every project in the organization (docs):
Custom result states are available organization-wide and apply to all projects.
This works well when every project shares the same testing process, but it breaks down as soon as different teams run different workflows.
What we’d like
The ability to scope custom result states to a specific project — for example:
-
Define result states per project (in Project settings), in addition to or instead of the org-wide set, or
-
Keep the org-wide set as a shared default, but let each project enable/disable or extend it with its own states.
Either approach would let each team tailor result states to its own workflow without affecting others.