Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Evaluation Form validates uniqueness of Phase #237

Open
3 tasks done
Tracked by #65
stepchud opened this issue Oct 25, 2024 · 0 comments · May be fixed by #294
Open
3 tasks done
Tracked by #65

Evaluation Form validates uniqueness of Phase #237

stepchud opened this issue Oct 25, 2024 · 0 comments · May be fixed by #294
Assignees

Comments

@stepchud
Copy link
Contributor

stepchud commented Oct 25, 2024

What/Why

A Challenge Phase can have one and only one Evaluation Form associated. This means there should be a unique index on the evaluation_forms.phase_id. Users should not be able to select a Phase for a new or existing Form that already has a different Form associated with it.

Acceptance Criteria

  • evaluation_forms table has a unique index on phase_id
  • EvaluationForm model has a Rails validates :phase_id, :uniqueness
  • The list of challenge phases on the Create/Edit Evaluation Form view should have phases with existing forms filtered out and not available for the user to select in the first place
@stepchud stepchud changed the title Evaluation Form validates uniqueness of Challenge / Phase Evaluation Form validates uniqueness of Challenge Phase Oct 25, 2024
@stepchud stepchud changed the title Evaluation Form validates uniqueness of Challenge Phase Evaluation Form validates uniqueness of Phase Oct 25, 2024
@r-bartlett-gsa r-bartlett-gsa added this to the Sprint 11/19/24 milestone Nov 6, 2024
@cpreisinger cpreisinger self-assigned this Nov 18, 2024
@r-bartlett-gsa r-bartlett-gsa linked a pull request Nov 26, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants