hackforla / hackforla/311-data

PRD - Determine requirements for support issues from contact page

Open
#1,769 6 comments 0 reactions 1 assignee Claimed by @rayneng View on GitHub
Complexity: Large Feature: automations Feature: Communication Feature: User Feedback p-feature: Contact Us Pre-Launch Role: Product Management size: 2pt
Dominant language
JavaScript
Stars
73
Forks
74
PR merge metrics
No merged PRs in 30d

Description

### Overview
We need to outline a project proposal for a Contact Form admin dashboard, so that all team members can understand how our admin dashboard will work before we make tickets to implement it.

### More Info
Major Components
- We need to come up with the labels, milestone, and project board info for support tickets that are opened when a user submits feedback from the contact page.
- We need to come up with the various routines needed in Google App Script to accomplish the features required by our admin dashboard
- We should document any existing infrastructure for automated email templates that we have completed leading up to this dashboard creation

### Action Items

Support Tickets and Submission Review Tickets
- [x] determine title
- [x] determine issue body
- [x] include all fields from the form itself (e.g. first-name, last-name, email, association, message)
- [x] determine what our action items should be in order to close the support ticket
- [x] determine which labels to use, if any
- [x] determine if it needs a milestone, if any
- [x] Determine if we should add it to our existing support board, or create a new one
- [x] Review: https://github.com/hackforla/311-data/issues/1797
- [ ] outline a support ticket template (in case we need to do any by hand)
- [ ] outline a submission review ticket
- [ ] complete Overview section, so that new readers can have a sense of what is in the document and how to navigate it
- [ ] Investigate if we can kick off Google App Scripts from Github Actions
- See: https://github.com/google/clasp/tree/master/docs
- [ ] Obtain review from leads
- [ ] Create new issues in Contact page epic

#### Ticket Bookkeeping
- https://github.com/hackforla/311-data/issues/1900
- [ ] remove the dependency label
- [ ] move the ticket to New Issue Approval
- [ ] add "ready for dev lead" label

### Resources/Instructions

#### 🔑 Deliverables 🔑
- [Google Doc with support ticket requirements](https://docs.google.com/document/d/1RbAXLbBVLVLiYCnA8CpplyygXu-cum7y9KHt_TgpWLU/edit?tab=t.0)
- [CONTACT_DASHBOARD_LIVE](https://docs.google.com/spreadsheets/d/1LA6GyjyqrUrylpCGrd0c6Lcf1c04Dk1QtH7O0Cg2xUQ/edit?gid=1614586410#gid=1614586410) (requires PII access permissions)

#### Other Resources
- [existing Support Project Board](https://github.com/hackforla/311-data/projects/5)
- [311 Data labels](https://github.com/hackforla/311-data/labels)
- [311 Data Milestones](https://github.com/hackforla/311-data/milestones?direction=asc&sort=title&state=open)

#### Screenshots

Screenshot of Contact Page Form

![image](https://github.com/user-attachments/assets/44397c0b-4cc5-49a9-88fe-08f2c1f3c98c)

Screenshot of Contact Page Form (OLD)

All the fields present in the contact page form
![image](https://github.com/hackforla/311-data/assets/6414668/229be780-4d26-4622-9f5d-a131c668e407)


Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.