[VW-344] Parsing Work Orders From Emails#151
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
| url: "/advisories", | ||
| }, | ||
| { | ||
| title: "Tracking", |
There was a problem hiding this comment.
Renaming Tracking to Work Orders purely in the UI.
Might be worthy as it's own chore ticket to rename all instances of Tracking to Work Orders in the actual filename, code & comments.
There was a problem hiding this comment.
The branch in the email classifier.
work order -> Actionable Requests
notification -> Informational emails
leans towards notif if unsure
There was a problem hiding this comment.
Pulls any relevant work order info from an email if found
Fields
Summary
Category
ScheduleAt
Assignee
Department
There was a problem hiding this comment.
Do we want to keep track of general work orders? Expanded out the relevance due to the bulk of the work orders on teamplay Fleet being general maintenance
There was a problem hiding this comment.
Adding an original email description tab for work orders generated from an email
(See PR summary for a screenshot)
and more tracking -> work order changes
There was a problem hiding this comment.
Adding a VIPER automation service user for work order tickets
1 participant
Adding support to parse Work Orders from forwarded Emails
Email Classification pipeline now attempts to classify a
Notificationor aWork OrderAdded
Original EmailDescription Tab for Work Orders Derived from Emails