bcgov / bcgov/entity

Scenario: The user wants to maintains the platform information

Open
#24,089 1 comment 0 reactions 0 assignees View on GitHub
Platform/Dashboard STR2
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

**Given** the platform information has been created
**When** the user is on the Dashboard page
**Then** they can edit the platform’s record, which includes:
- Representatives names and contact details
- Addresses, Mailing and Attorney if assigned
- List of Brands

--
- [x] UX /UI Design
- [ ] API Services
- [ ] UI Build
- [ ] QA

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Dashboard page and the existing platform-information record flow, then trace how representatives, addresses, attorneys, and brands are represented in the API and UI. The issue names no files or tests; done means the API services, UI build, and QA checklist are completed for editing all listed platform information.

Written by the indexing model from the issue text.

Assessment

Tech stack
flask, javascript, postgres, python
Domain
full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.