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

As a data analyst, I need to know when my data has been processed with or w/o errors #2509

Closed
4 of 13 tasks
andrew-jameson opened this issue May 2, 2023 · 6 comments · Fixed by #2959
Closed
4 of 13 tasks
Assignees
Labels
dev Parity Work associated with TDP Parity

Comments

@andrew-jameson
Copy link
Collaborator

andrew-jameson commented May 2, 2023

Description:
Generate email to STT data analysts for error reports on submitted datafiles. this email will replace the current data submission email that STT users currently receive.

Acceptance Criteria:

  • Aligned with design spec ("Near Term Lower-lift" version):
    • Data analysts receive email notification that their data is processed
    • Email subject leads with whether or not their data file had errors
    • Email table contains columns for section, submitted by, and error report (Error Report Available/No Errors being possible values)
    • Email body contains copy on where to access the error report in TDP and where to go for more information in the knowledge center
  • Replaces existing notifications for data file submission
  • Testing Checklist has been run and all tests pass
  • README is updated, if necessary

Tasks:

  • Create new email template here
  • Find conditional/trigger for when error reports are ready
  • Test null values for all variables
  • Remove old email template for data submission**
  • Run Testing Checklist and confirm all tests pass

Notes:

  • Pull in after 1) Parsing Enhancements and 2) Error Messaging epics are complete.

Supporting Documentation:

Screenshot w/ replacement tags
image

Screenshot w/ example values
image

Open Questions:

@Smithh-Co
Copy link

@lilybl1 @reitermb Hi team, post backlog refinement 5.9, we need updated copy for this ticket regarding a figma/html template and alignment on content/CTA wording to current errors research prototypes.

Tagging this as high priority for development ahead of v3.3 as well - TY

@reitermb reitermb changed the title As a data analyst, I need to know when my error report is ready As a data analyst, I need to know when my error report is ready (or my data has been processed) Jul 8, 2023
@reitermb reitermb changed the title As a data analyst, I need to know when my error report is ready (or my data has been processed) As a data analyst, I need to know when my data has been processed Jul 8, 2023
@reitermb reitermb changed the title As a data analyst, I need to know when my data has been processed As a data analyst, I need to know when my data has been processed (and whether it has errors) Jul 8, 2023
@reitermb reitermb changed the title As a data analyst, I need to know when my data has been processed (and whether it has errors) As a data analyst, I need to know when my data has been processed with or w/o errors Jul 11, 2023
@andrew-jameson andrew-jameson self-assigned this Feb 13, 2024
@reitermb
Copy link

2pts left depending on unit tests

@robgendron
Copy link

2 points remaining.

@jtimpe jtimpe assigned jtimpe and unassigned andrew-jameson Apr 22, 2024
@lfrohlich
Copy link
Collaborator

@ttran-hub could you do an a11y review?

@reitermb
Copy link

reitermb commented May 6, 2024

image

Refreshed a11y review from the Raft side. Noting that the 3 errors listed there are regarding the control at the top to toggle between nearer and later term versions of the email template, not the template itself--so this is equivalent to a clean scan for the actual content being evaluated.

cc @ttran-hub

@ttran-hub
Copy link
Collaborator

a11y 🚀LGTM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev Parity Work associated with TDP Parity
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants