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

UI - Staff Correction page (Part 2) #2654

Closed
9 of 11 tasks
severinbeauvais opened this issue Feb 12, 2020 · 5 comments
Closed
9 of 11 tasks

UI - Staff Correction page (Part 2) #2654

severinbeauvais opened this issue Feb 12, 2020 · 5 comments
Assignees
Labels
ENTITY Business Team

Comments

@severinbeauvais
Copy link
Collaborator

severinbeauvais commented Feb 12, 2020

Implement filing page that allows staff to file a correction for a given filing.

Acceptance Criteria

See comments in wireframes for additional AC.

Wireframes:
https://preview.uxpin.com/d834cac627a4d83ee91678dfc66f1b2bca0259c8#/pages/123119265

Wireframes for the Business Dashboard for reference:
https://preview.uxpin.com/cefa7724eb7ad8538cb92f016364066b202fbec2#/pages/123078669/simulate/no-panels

@severinbeauvais
Copy link
Collaborator Author

@severinbeauvais
Copy link
Collaborator Author

I increased the estimate to account for updating the other filings (re: Staff Payment changes) and because some form validation took longer than expected.

@severinbeauvais
Copy link
Collaborator Author

I increased the estimate to account for extra work required to resume a draft filing.

@severinbeauvais
Copy link
Collaborator Author

Test Notes

In addition to the correction filing page, the Staff Payment component and functionality was updated for all filings. Therefore, please verify:

  • toggle Payment Received / No Fee radio buttons
  • toggle Priority checkbox
  • try the above before and after making a filing change (esp AR with COA/COD)
  • try the above after resuming a draft

@severinbeauvais
Copy link
Collaborator Author

I updated the estimate to time actually consumed.

It took an extra day because I refactored some new (common) functionality into a mixin and typed a lot of stuff along the way (re: type strictness).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ENTITY Business Team
Projects
None yet
Development

No branches or pull requests

3 participants