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

[Story] Receive report on Vendor platform activity #263

Open
4 tasks
angelcardoz opened this issue Sep 26, 2024 · 0 comments
Open
4 tasks

[Story] Receive report on Vendor platform activity #263

angelcardoz opened this issue Sep 26, 2024 · 0 comments
Labels

Comments

@angelcardoz
Copy link
Contributor

Epic

Epic issue includes overview, complete list of user stories, technical and content requirements, user testing task ideation, and current design mock-ups.

User story

  • As the Vendor Outreach Coordinator, I want to receive a bi-weekly report on Vendor platform activity, so that I can track engagement and make informed decision for targeted outreach efforts.

Acceptance criteria

  • Report Frequency: A report should be automatically generated and delivered every two weeks.
  • Report Delivery: The report should be sent via email to the Vendor Outreach Coordinator's email address.
  • Report Format: The report should be provided in clear and readable format, such as PDF or body of an email.
  • Cumulative Data Set: The data set should build upon itself over time, incorporating all previous data up to the current point.
  • Content Detail: The report should include the following details about Vendor activity:
    • Name of vendor who visited the platform.
    • Number of times each vendors visited the platform.
    • Duration of each visit.
    • Whether the vendor has uploaded a test file.
    • Date of last visit.
  • Data Privacy: Ensure that the report complies with data privacy, anonymizing data as needed.
  • Error Handling: If there is an error generating or sending the report, an alternative email should be set notifying the Vendor Outreach Coordinator of the issue.

Technical tasks

Developers should create technical tasks and add links (below) prior to sprint planning.

Front end

  • Task (link)
  • Task (link)

Back end

  • Task (link)
  • Task (link)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant