使用者故事撰寫

Story 1: Export a report as PDF

As a report user,
I want to export a report as a PDF,
so that I can save, print, or share a fixed-format version.

Acceptance criteria

1. Given I have permission to view a report, when I select “Export as PDF,” then the system generates a PDF containing the report’s current data and visible configuration.
2. Given the PDF is generated successfully, when generation completes, then the file downloads with a meaningful name that includes the report name and export date.
3. Given the report spans multiple pages, when the PDF is generated, then content is paginated without unintentionally cutting off tables, charts, or labels.
4. Given the report contains charts, tables, and filters, when it is exported, then those elements are readable and the applied filters are identified in the PDF.
5. Given PDF generation fails, when the failure occurs, then I receive a clear error message and can retry.

Edge cases

• The report contains no data.
• The report has very wide or long tables.
• The report contains unsupported fonts, characters, or visualizations.
• The report name contains special characters.
• The report changes or is deleted during PDF generation.
• The export exceeds file-size or processing-time limits.
• The user loses access before generation completes.

Size hint: L
Dependencies: Existing report rendering and authorization; PDF generation service or library; file download support.

Story 2: Configure a weekly report email schedule

As a report user,
I want to schedule a report for weekly email delivery,
so that recipients receive it automatically without manual exports.

Acceptance criteria

1. Given I can view and schedule a report, when I create a schedule, then I can select a weekday, delivery time, time zone, and one or more valid email recipients.
2. Given all required scheduling fields