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.
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
Acceptance criteria
Technical tasks
Developers should create technical tasks and add links (below) prior to sprint planning.
Front end
Back end