active 2024-01-18 → 2024-04-25 (UTC)
Complete coverage26,689 / 26,689 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-08-31 (UTC)
Events
50
Pushes
3
Pull requests
0
Issues
44
Stars
0
Forks
0
Activity over time
Daily event counts in the loaded window
Line chart, 99 days from 2024-01-18 to 2024-04-25. Pushes: 3 total, peak 2 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 44 total, peak 24 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| jclemons555 | 21 | 3 | 0 | 0 |
| Esauh | 13 | 0 | 0 | 0 |
| ashaanderson | 7 | 0 | 0 | 0 |
| brianP1201 | 6 | 0 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue#47jclemons5552024-04-10 21:555.6 add survey.js java script functionality, implement survey component when displaying web app
- Issue#46jclemons5552024-04-10 21:505.5 design and format updated post-call survey utilizing survey js
- Issue#45jclemons5552024-04-10 21:345.4 fix css and html formatting to fix multiple devices
- Issue#44brianP12012024-04-09 20:36Add additional agent information to the recent calls page.
- Issue#43brianP12012024-02-14 18:42Research GraphQL Integration with AWS Amplify
- Issue#42Esauh2024-01-31 18:27Host the site on amplify so people do not have to run our script locally to view the web app
- Issue#40Esauh2024-01-23 17:417.2: Retrieve call/text chat data information from an individual call through the AWS Connect api
- Issue#39Esauh2024-01-23 17:417.1: Go through AWS Connect API documentation
- Issue#38jclemons5552024-01-23 17:375.3: Reduce the number of mandatory fields to the essential information needed for feedback. Ensure the interface is easily accessible and encourages users to provide detailed feedback
- Issue#37ashaanderson2024-01-23 17:359.3 Implement Feedback Moderation and Quality Assurance
- Issue#36ashaanderson2024-01-23 17:349.2 Implement User Feedback Notifications
- Issue#35jclemons5552024-01-23 17:335.2: Organize the feedback form with logical sections, making it easy for users to navigate. Group related fields together and maintain a logical flow from one section to the next.
- Issue#34ashaanderson2024-01-23 17:339.1 Implement Feedback Contextualization and Search
- Issue#33brianP12012024-01-23 17:326.4: Include contact details of the customer, and the representative in case of an ongoing incident or if additional follow-up is necessary.
- Issue#32brianP12012024-01-23 17:326.3: Implement the ability for the Amazon representative to escalate the incident details to a Manager, if deemed necessary.
- Issue#31brianP12012024-01-23 17:326.2: Implement a post-call feedback survey form that is accessible by both the customer and Amazon representative.
- Issue#30ashaanderson2024-01-23 17:322.3 Implement Feedback Analytics and Reporting
- Issue#29brianP12012024-01-23 17:326.1: Implement the ability to track the customer service representative for each call.
- Issue#28ashaanderson2024-01-23 17:312.2 Implement Feedback Review and Management System
- Issue#27ashaanderson2024-01-23 17:302.1 Enable Audio-Based Feedback with Voice Memo Recording
- Issue#26ashaanderson2024-01-23 17:26Develop a user interface for text-based feedback
- Issue#25jclemons5552024-01-23 17:255.1: Implement a straightforward layout with easily identifiable elements
- Issue#24jclemons5552024-01-23 17:229.2: Implement functionality that allows the caller to input representative information
- Issue#23jclemons5552024-01-23 17:149.1 Implement functionality that references caller identification information
- Issue#21jclemons5552024-01-23 17:072.3: Design an intuitive and responsive user interface that includes a text area for feedback input, relevant labels, and any additional options
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.