Is your feature request related to a problem?
There are two issues in the Assessment config wizard: Users cannot see all configured pipeline stages in the Review step and are misled by the labeled button in the Evaluation step, causing confusion and potential errors. Additionally, saving an Evaluation config incorrectly appends versions, and the ASSESSMENT tag is not carried through.
Describe the solution you'd like
- Relabel Evaluation's forward button to Next: Post Processing (Mapper → Eliminatory → Evaluation → Post Processing → Review).
- Add Eliminatory and Post Processing sections to Review, each with a Skipped state when unconfigured; collapsible, with Edit linking back to the owning step.
- Ensure saving always creates a new config (removing name-match auto-merge).
- Forward
tag=ASSESSMENT from saveAssessmentConfig through the versions BFF route to the backend.
Original issue
Is your feature request related to a problem?
Two gaps in the Assessment config wizard:
- Review visibility — the Review step omits the two optional pipeline stages (Eliminatory pre-filters, Post Processing), so users can't confirm what's configured or that a stage was skipped before submitting. The Evaluation step also mislabeled its forward button "Next: Review", skipping the Post Processing step in wizard order.
- Config save — saving an Evaluation config silently appended a new version to any existing config with a matching name, instead of creating a distinct config. Separately, config version creation did not carry the
ASSESSMENT tag through the BFF to the backend, so assessment versions weren't tagged correctly.
Describe the solution you'd like
- Relabel Evaluation's forward button to Next: Post Processing (Mapper → Eliminatory → Evaluation → Post Processing → Review).
- Add Eliminatory and Post Processing sections to Review, each with a Skipped state when unconfigured; collapsible, with Edit jumping back to the owning step.
- Save always creates a new config (drop the name-match auto-merge).
- Forward
tag=ASSESSMENT from saveAssessmentConfig through the versions BFF route to the backend.
Is your feature request related to a problem?
There are two issues in the Assessment config wizard: Users cannot see all configured pipeline stages in the Review step and are misled by the labeled button in the Evaluation step, causing confusion and potential errors. Additionally, saving an Evaluation config incorrectly appends versions, and the
ASSESSMENTtag is not carried through.Describe the solution you'd like
tag=ASSESSMENTfromsaveAssessmentConfigthrough the versions BFF route to the backend.Original issue
Is your feature request related to a problem?
Two gaps in the Assessment config wizard:
ASSESSMENTtag through the BFF to the backend, so assessment versions weren't tagged correctly.Describe the solution you'd like
tag=ASSESSMENTfromsaveAssessmentConfigthrough the versions BFF route to the backend.