-
Notifications
You must be signed in to change notification settings - Fork 59
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
Special Resolution Corrections - Save/Resume + File and Pay #15502
Comments
Missing an ledger update scenario @jennyschan
|
Do we also want to include save as draft scenario for correction ? @jennyschan |
@ethantspitt Added "Save and Resume later" scenario #4. thx |
Hey team! Please add your planning poker estimate with Zenhub @Jxio @piahmed @seeker25 |
Removing UXA label, created an overall ux review ticket: #16782 |
move this ticket to review, new ux issue will be handled by ticket 16782 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Acceptance Criteria
Scenario 1: Starting a Correction Covered by 16213
Scenario 2: Specifying what type of correction Covered by 16213
This is the same as the other correction filings existing in the system
Scenario 3a: Correcting the Special Resolution with "Client Error" option Covered by 15951
*AND ... After made the correction, Completing Party, Details, and Certify sections will need to be entered to enable the File and Pay button. if Staff Error these sections will not be displayed.
Scenario 3b: Correcting the Special Resolution with "Staff Error" option Covered by 15951
*AND .... After made the correction, the payment option will be defaulted to "No Fee"
Scenario 4: Able to Save and Resume later
Scenario ?? : display court order component
Scenario 5: Paying for Correction
Scenario 6: After File and Pay for Correction
Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)
Validation Rules? (If yes, list here)
UX Design
https://preview.uxpin.com/53053d7aeb85fb29915f7afa596429aea4f2a964#/pages/161307726/simulate/sitemap
Link to DoR for a US/ Feature
https://github.com/bcgov/entity/blob/master/.github/ISSUE_TEMPLATE/DoR%20-%20Relationships.md
https://github.com/bcgov/entity/blob/master/.github/ISSUE_TEMPLATE/DoR%20-%20Entity.md
Link to the DoD for a US/ Feature
https://github.com/bcgov/entity/blob/master/.github/ISSUE_TEMPLATE/DoD%20-%20Relationships.md
https://github.com/bcgov/entity/blob/master/.github/ISSUE_TEMPLATE/DoD%20-%20Entity.md
The text was updated successfully, but these errors were encountered: