Evaluation Form: Create and Edit

[r-bartlett-gsa]

User Story

As a challenge manager, in order to provide evaluators a form that they can use for scoring submissions, I would like to be able to create new, view or edit already created evaluation forms.

Acceptance criteria:

• [ ] A challenge manager can create an evaluation form from the evaluation forms list view, and the user is taken to an evaluation form creation page
  • [ ] An Evaluation Form Creation Page allows the user to setup a new evaluation form in a step-by-step process
  • [ ] Enter form information
    • [ ] Form title
    • [ ] Assign the form to a challenge and a challenge phase, #65
    • [ ] Form instructions
  • [ ] Enter evaluation criteria details, #67, #69, #68
  • [ ] Enter publication date and closing date
    • [ ] Publication date makes the form available for use by evaluators
    • [ ] Evaluation form publication date cannot be sooner then the challenge it's assigned to close date
    • [ ] Closing date disables the form from being used by evaluators
    • [ ] The dates activate at midnight EST
  • [ ] A challenge manager can save the form as a draft, which saves the form as is and it can be edited a a later time
    • [ ] Required fields may be left blank
    • [ ] A confirmation is displayed with options to edit the form
    • [ ] Draft form cannot go live on a publication date
    • [ ] This sets the form in "draft" status - the form continues to be editable by the challenge managers and is not available for the evaluators
  • [ ] A challenge manager can publish the form, which makes the form complete and disables future editing of the form
    • [ ] All required fields must be provided
    • [ ] The form must have at least one evaluation criteria
    • [ ] A confirmation is displayed with an option to assign evaluators, #75
    • [ ] Only a published form goes live on a scheduled publication date
    • [ ] This sets the form in "published" status - the form cannot be editable by the challenge managers and it is available for the evaluators between publication and closing dates
• [ ] In-line validation messages are displayed in addition to error messages that appear at the top of the form (per USWDS guidance)
• [ ] A challenge manager can edit an evaluation form that is in draft status from the evaluation forms list view
  • [ ] Editing a draft form opens a previously saved form draft and allows the user to continue filling in form information and fields as outlined above
• [ ] A challenge manager can view an evaluation form that is published status from the evaluation forms list view, #104

Development tasks:

• [ ] #159
• [ ] #160
• [ ] #161
• [ ] #162
• [x] #163
• [ ] #164
• [ ] #165
• [ ] #167
• [ ] #168

Definition of Done

Doing (dev team)

• [ ] Code complete
• [ ] Code is organized appropriately
• [ ] Any known trade offs are documented in the associated GH issue
• [ ] Code is documented, modules, shared functions, etc.
• [ ] Automated testing has been added or updated in response to changes in this PR
• [ ] The feature is smoke tested to confirm it meets requirements
• [ ] Database changes have been peer reviewed for index changes and performance bottlenecks
• [ ] PR that changes or adds UI
  • [ ] include a screenshot of the WAVE report for the altered pages
  • [ ] Confirm changes were validated for mobile responsiveness
• [ ] PR approved / Peer reviewed
• [ ] Security scans passed
• [ ] Automate accessibility tests passed
• [ ] Build process and deployment is automated and repeatable
• [ ] Feature toggles if appropriate
• [ ] Deploy to staging

• [ ] Move card to testing column in the board

  Staging

• [ ] Accessibility tested (Marni)
  • [ ] Keyboard navigation
  • [ ] Focus confirmed
  • [ ] Color contrast compliance
  • [ ] Screen reader testing
• [ ] Usability testing: mobile and desktop (Tracy or Marni)
• [ ] Cross browser testing (tool to be determined) (Tracy or Marni)
  • [ ] UI rendering is performant
• [ ] AC review (Renata)
• [ ] Deploy to production (production-like environment for eval capability) (dev team)

• [ ] Move to production column in the board

  Production

• [ ] User and security documentation has been reviewed for necessary updates (Renata/Tracy/Dev team)
• [ ] PO / PM approved (Jarah or Renata)
• [ ] AC is met and it works as expected (Jarah or Renata)
• [ ] Move to done column in the board (Jarah or Renata)

[r-bartlett-gsa]

[r-bartlett-gsa]

Confirmation views:

[stepchud]

This seems like 3 different stories that can be built separately

[r-bartlett-gsa]

This seems like 3 different stories that can be built separately

@stepchud I'm happy to split this into three, but the way I was looking at it, is that the meat of the work is in "Create", the "Edit" is the same as create with some of the fields prefilled, and "View" is the same as edit with fields prefilled and the user cannot edit any of the fields.