Reg\Operator - Wording updates for operator access pages - Githubissues

bcgov / cas-registration

A web app for Registration in OBPS under the Clean Growth branch

Apache License 2.0

1 stars 1 forks source link

Reg\Operator - Wording updates for operator access pages #2413

Open zoeyli-46 opened 1 month ago

zoeyli-46 commented 1 month ago

Description:

The operator access pages wording needs to be replaced

Acceptance Criteria:

Update the following pages when an operator exists but is missing the admin Wireframe for requesting access Wireframe for pending access Wireframe for declined access

Update the following page when an operator exists and a non-admin is requesting access to it Wireframe

Development Checklist:

[ ] Checklist item
[ ] Checklist item
[ ] Checklist item
[ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

·Definition of Done (Note: If any of these points are not applicable, mark N/A)

[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
[ ] Reviewed and approved by Product Owner

Notes:

zoeyli-46 commented 1 month ago

@andrea-williams @patriciarussellCAS here is the ticket for the wording updates for the operator access pages. (replacing operation representative, etc.) cc @patrickisaac