bcgov / bcgov/alcs

Other department view of C&E file (V2)

Open
#2,901 0 comments 0 reactions 0 assignees View on GitHub
User Story
Dominant language
TypeScript
Stars
10
Forks
0
Avg merge
20h 8m
Merged PRs (30d)
30

Description

As LUP, GIS and Soil Officers, I want to see some insensitive and high level data in the CE& file so I can help myself or call up the assigned officer for more info.

**Acceptance Criteria**

- [ ] create a sanitized view for users without the C&E role, where they can see:
- [ ] Header
- [ ] Show all content but remove editing on
- [ ] Assign officer / Edit assigned officer
- [ ] Overview
- [ ] Status (no editing)
- [ ] Complaint / Referral
- [ ] Overview section without 'Edit Section' button
- [ ] (Hide Submitter section)
- [ ] (Hide the Complaint / Referral document table and contents)
- [ ] Owner & Contacts
- [ ] Property Owner section without:
- [ ] 'Edit Section' button
- [ ] Inline editing
- [ ] (Hide the Owner documents)
- [ ] Property & Maps
- [ ] Property section without Edit Section button
- [ ] Maps (include + Maps button and CRUD in document table)
- [ ] Chronology -> should already be like this
- [ ] All content will be hidden
- [ ] Disable the tab and provide hover text: Contact assigned officer
- [ ] Documents
- [ ] All content will be hidden
- [ ] Disable the tab and provide hover text: Contact assigned officer
- [ ] If a user has both a C&E role and non-C&E role, show them the C&E view
- [ ] How do we want this to work for the Admin user?

Figma: https://www.figma.com/design/5qXmbgyOL5M8PO7m7oqCeR/ALCS?node-id=7149-22962&t=c3bwRLWxpPcNsNdR-4

Confirm this task meets our team [**Definition of Ready (DoR)**](https://www.figma.com/board/XmNkN600aAVWFCBmSDdt10/Team-Documents?node-id=1-2&t=Xjd6nHZZ7YlnoOrD-4) before moving to the **Next Sprint** column.

Confirm this task meets our team [**Definition of Done (DoD)**](https://www.figma.com/board/XmNkN600aAVWFCBmSDdt10/Team-Documents?node-id=3-21&t=Xjd6nHZZ7YlnoOrD-4) before moving to the **Done** column.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the current C&E file view and the role-handling entry points, using the acceptance criteria and linked Figma design as the behavior reference. Confirm how users with C&E and non-C&E roles are prioritized, resolve the unspecified Admin behavior, and verify that restricted sections, tabs, editing controls, and map documents match the criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authorization, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.