Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Internal Dashboard: Most active hour #2908

Closed
AkhileshNegi opened this issue Jul 15, 2023 · 1 comment · Fixed by #2923
Closed

Internal Dashboard: Most active hour #2908

AkhileshNegi opened this issue Jul 15, 2023 · 1 comment · Fixed by #2923
Assignees
Labels
C4GT Community Code for GovTech

Comments

@AkhileshNegi
Copy link
Member

Description

Improving Internal Dashboard by adding a few more metrics

Goals

To see a high-level idea of the most active time of the chatbot add a bar chart for the count of different messages across hours. Use stats table with a period as hour

Project Name

Glific

Organization Name

Project Tech4Dev

Domain

Social Sector

Complexity

Easy

Tech Skills Needed

Elixir, Liveview

Mentor(s)

@AkhileshNegi

Category

Feature

Product Set-Up

https://github.com/glific/

Acceptance Criteria

PR merged into the main branch

@AkhileshNegi AkhileshNegi added the C4GT Community Code for GovTech label Jul 15, 2023
@c4gt-community-support
Copy link

c4gt-community-support bot commented Jul 15, 2023

Hi!
Mandatory Details - The following details essential to submit tickets to C4GT Community Program are missing. Please add them!

  • Complexity must be High/Medium/Low

Without these details, the ticket cannot be listed on the C4GT Community Listing.

Important Details - These following details are helpful for contributors to effectively identify and contribute to tickets.

  • Sub-Category - Please mention the sub-category if any for the ticket

Please update the ticket

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C4GT Community Code for GovTech
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants