Skip to main content

Email Sending

8 requirements · 19 scenarios

Email Threading with Interim Messages

JR-email-sending-001
The system SHALL persist interim progress messages to the mailbox so they can be replied to for proper email threading. The final response SHALL reply to the interim message to maintain thread continuity.
2 test scenarios
  • Interim message saved to sent items JR-email-sending-001.1
  • Final message replies to interim message JR-email-sending-001.2

Interim Acknowledgement for Processing

JR-email-sending-002
The system SHALL send a short interim acknowledgement email when invoking a long-running operation on the email channel so the user knows the request is being processed. The interim message SHALL be sent at most once per email thread. The interim acknowledgement SHALL NOT be sent for non-email channels.
2 test scenarios
  • Interim sent once per thread for long operation JR-email-sending-002.1
  • Interim skipped for chat channel JR-email-sending-002.2

ETA in Translation Acknowledgements

JR-email-sending-003
When sending interim acknowledgements for translation operations, the system SHALL include a user-facing estimated time of completion range.
1 test scenario
  • Translation interim includes ETA range JR-email-sending-003.1

Interim Message Cleanup

JR-email-sending-004
The system SHALL delete interim messages after the final response is successfully sent to keep the mailbox clean. If no interim message was sent, no cleanup SHALL be attempted.
2 test scenarios
  • Final message triggers interim deletion JR-email-sending-004.1
  • No cleanup when no interim exists JR-email-sending-004.2

Email Threading Fallback

JR-email-sending-005
The system SHALL fall back to regular email sending if the threading target message cannot be found, ensuring delivery is never blocked by a missing thread parent.
1 test scenario
  • Reply falls back when target not found JR-email-sending-005.1

Smart Snippet View for Edits

JR-email-sending-007
The system SHALL display edit instructions directly above their corresponding paragraph snippets in a unified view, replacing separate sections for documents edited and edit snippets. Multiple edits to the same paragraph SHALL be grouped together. Snippets SHALL be ordered by document position.
5 test scenarios
  • Single edit with single paragraph JR-email-sending-007.1
  • Multiple edits to same paragraph grouped JR-email-sending-007.2
  • Multi-insert paragraphs grouped together JR-email-sending-007.3
  • Multi-insert with additional edits split out JR-email-sending-007.4
  • Ordering by document position JR-email-sending-007.5

Edit Citation Display

JR-email-sending-009
The system SHALL display edit citation information in the snippet view to show users the source of each edit. Citations SHALL appear below the instruction text.
3 test scenarios
  • Playbook citation displayed below instruction JR-email-sending-009.1
  • Multiple instructions with same playbook source JR-email-sending-009.2
  • No citation available handled gracefully JR-email-sending-009.3

Playbook Indicator in Email

JR-email-sending-010
The system SHALL display a playbook indicator in the email when edits originated from a playbook analysis. Emails without playbook-sourced edits SHALL omit the indicator. Mixed-source emails SHALL indicate both sources.
3 test scenarios
  • Edits from single playbook show indicator JR-email-sending-010.1
  • No playbook edits omit indicator JR-email-sending-010.2
  • Mixed sources show both indicators JR-email-sending-010.3
All Specs