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

Dashboard/Jobs/Templates: Improve how we display data #1302

Open
3 of 11 tasks
em-herrick opened this issue Mar 13, 2024 · 2 comments
Open
3 of 11 tasks

Dashboard/Jobs/Templates: Improve how we display data #1302

em-herrick opened this issue Mar 13, 2024 · 2 comments

Comments

@em-herrick
Copy link
Contributor

em-herrick commented Mar 13, 2024

Description

Current goal: synthesizing user feedback and developing implementation plan

Message information is hard to find, displayed on a few different pages in different formats, and are questionably accurate (e.g. delayed). How can we better organize schedule and sent message information to be more useful to different users?

Hypothesis is that users need message information organized by:

  • Individual jobs
  • Individual Users
  • Templates or folders - across relevant jobs and senders
  • Service(s)

We will display scheduled and sent information on the following pages:

  • Dashboard
  • Activity/Jobs
  • Templates (emerging)

Delivery Outcomes

Decrease confusion of where to find sent and scheduled messages, their delivery status, and what these statuses mean, measured by more partner agencies using this status information in their outreach and outcome tracking activities.

Features (in order of priority/focus)

NOW:
Improve API Endpoints for front-end usage

Ship: Allowance Countdown with Chart JS

Ship: 7-day service-level dashboard data viz

Ship: 7-day indvidual-level dashboard data viz


NEXT:
Ship: Yearly (month-by-month) service-level dashboard data viz


DONE:
Feature: Research and Testing

@em-herrick em-herrick changed the title UX Epic: Display and download delivery statuses UX: Display and download delivery statuses Mar 13, 2024
@maomeara63
Copy link

  • Review statuses returned by AWS and how they are used in Notify (in app and in reports)
  • Map returned statuses to desired state to be presented to partners
  • Provide description of what is in each state
  • Review documentation
  • Implement

@maomeara63 maomeara63 self-assigned this Mar 27, 2024
@em-herrick em-herrick changed the title UX: Display and download delivery statuses Improve how we display/export message status information Apr 24, 2024
@stvnrlly stvnrlly removed the epic label Apr 24, 2024
@em-herrick em-herrick added epic and removed UI/UX labels Apr 24, 2024
@em-herrick em-herrick changed the title Improve how we display/export message status information Improve how we display (and allow users to download) message status information Apr 25, 2024
@em-herrick em-herrick assigned em-herrick and unassigned em-herrick Apr 25, 2024
@em-herrick em-herrick self-assigned this Apr 25, 2024
@em-herrick em-herrick changed the title Improve how we display (and allow users to download) message status information Improve how users can view and download message status information May 6, 2024
@em-herrick em-herrick changed the title Improve how users can view and download message status information Improve how users can view message status information May 6, 2024
@em-herrick em-herrick changed the title Improve how users can view message status information Dashboard? (improve how we display data) May 8, 2024
@em-herrick em-herrick changed the title Dashboard? (improve how we display data) Dashboard/Jobs/Templates: Improve how we display data May 8, 2024
@em-herrick em-herrick assigned anagradova and unassigned maomeara63 Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Epics - In-progress
Development

No branches or pull requests

6 participants