You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a cas-director user, I should have all functionalities listed in this table.
Acceptance Criteria:
Manage first-time operator admin role approvals
Assign BORO ID/BCGHG ID
Development Checklist:
migration to add the cas_director role (e.g. of adding cas_analyst: cas-registration/bc_obps/registration/migrations/0002_prod_data.py)
in cas-registration/bciers/apps/registration/app/idir, create a cas_director folder. Copy/paste the structure of cas_admin into this folder (cas_director is allowed to access everything)
add cas_director to the "access_roles" in the internal.json files to give cas_director users access to all dashboard tiles
Previously all internal users had the same permissions, so many parts of the app use an isInternalUser or isAuthorizedAdminUser variable to determine whether to show/hide/allow editing. Change these conditionals to only allow cas_director to assign bcghg id and boro id
first-time operator admin role approvals access is controlled by a dashboard tile (if users have the tile, they can do it) so no changes needed
Check and update the endpoint and service permissions for this new role to ensure the user has the correct access.
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:
The text was updated successfully, but these errors were encountered:
Dependencies
Description:
As a
cas-director
user, I should have all functionalities listed in this table.Acceptance Criteria:
Development Checklist:
cas-registration/bciers/apps/registration/app/idir
, create a cas_director folder. Copy/paste the structure of cas_admin into this folder (cas_director is allowed to access everything)internal.json
files to give cas_director users access to all dashboard tilesisInternalUser
orisAuthorizedAdminUser
variable to determine whether to show/hide/allow editing. Change these conditionals to only allow cas_director to assign bcghg id and boro idDefinition of Ready (Note: If any of these points are not applicable, mark N/A)
·Definition of Done (Note: If any of these points are not applicable, mark N/A)
Notes:
The text was updated successfully, but these errors were encountered: