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

Special Resolution Corrections - Save/Resume + File and Pay #15502

Closed
zac-broitman opened this issue Mar 1, 2023 · 6 comments
Closed

Special Resolution Corrections - Save/Resume + File and Pay #15502

zac-broitman opened this issue Mar 1, 2023 · 6 comments
Assignees
Labels
BA Pay Work for Pay Team STORY

Comments

@zac-broitman
Copy link

zac-broitman commented Mar 1, 2023

  • As a BC Registries Staff user
  • I want correct a coop's special resolution filing
  • so that I can fix any mistakes made on it

Acceptance Criteria

Scenario 1: Starting a Correction Covered by 16213

  • GIVEN ... I am a BC Registries Staff user and there is a special resolution filed for a coop I am viewing
  • WHEN ... I view and select that filing's options from the "Recent Filing History" section
  • AND ... click the View Document
  • THEN ... I should see the option to File a Correction

Scenario 2: Specifying what type of correction Covered by 16213

  • GIVEN ... I am a BC Registries Staff user and there is a special resolution filed for a coop I am viewing
  • WHEN ... I select to correct the filing
  • THEN ... I should be prompted to choose whether it is a Staff Error or a Client Error
    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

  • GIVEN ... I have selected to complete a correction on a Special Resolution
  • WHEN ... I selected the type of correction selection (Scenario 2)
  • THEN ... I should see the Special Resolution form pre-filled with the information provided and I should be able to change any of the inputs
    *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

  • GIVEN ... I have selected to complete a correction on a Special Resolution
  • WHEN ... I selected the type of correction selection (Scenario 2)
  • THEN ... I should see the Special Resolution form pre-filled with the information provided and I should be able to change any of the inputs
    *AND .... After made the correction, the payment option will be defaulted to "No Fee"

Scenario 4: Able to Save and Resume later

  • GIVEN ... I have selected to complete a correction on a Special Resolution
  • WHEN ... After I filled out the info for correction and pause for some reason
  • THEN ... I selected the button "Save and Resume later"
  • AND ...the correction will be displayed on the TO DO box to resume and complete correction

Scenario ?? : display court order component

  • GIVEN ... I have selected to complete a correction on a Special Resolution
  • WHEN ... display court order component when the correction is related court order or plan of arrangement
  • THEN ... I can enter the court order number or click the checkbox for plan of arrangement
  • AND ...user can proceed and complete correction

Scenario 5: Paying for Correction

  • GIVEN ... I have selected to complete a correction on a Special Resolution
  • WHEN ... I select to complete my correction
  • THEN ... I should see the payment selection and be required to pay a fee of $20.00 (if the correction is file with Client Error)

Scenario 6: After File and Pay for Correction

  • GIVEN ... I completed the correction on a Special Resolution
  • WHEN ... I select to complete my correction and click "File and Pay"
  • THEN ... The Correction displayed on my business dashboard "Recent File History" section with details

Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)

  • Do you know a possible contact person to reach out (from the other team)?

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

@ethantspitt
Copy link
Collaborator

ethantspitt commented Apr 19, 2023

Missing an ledger update scenario @jennyschan

  • showing a correction ledger entry
  • showing detail on the correction ledger
  • showing detail on the original special resolution filing (This filing was corrected on DATE).
  • either staff or client filing should have an Receipt output even when there's no fee.

@ethantspitt
Copy link
Collaborator

Do we also want to include save as draft scenario for correction ? @jennyschan

@jennyschan
Copy link

@ethantspitt Added "Save and Resume later" scenario #4. thx

@JohnamLane JohnamLane changed the title Special Resolution Corrections Special Resolution Corrections - Save/Resume + File and Pay May 3, 2023
@JohnamLane
Copy link
Collaborator

Hey team! Please add your planning poker estimate with Zenhub @Jxio @piahmed @seeker25

@ethantspitt
Copy link
Collaborator

Removing UXA label, created an overall ux review ticket: #16782

@Jxio
Copy link
Collaborator

Jxio commented Jun 27, 2023

move this ticket to review, new ux issue will be handled by ticket 16782

@PCC199 PCC199 closed this as completed Jul 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BA Pay Work for Pay Team STORY
Projects
None yet
Development

No branches or pull requests

7 participants