-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Overview
We have a very minimal example of a rules system implemented already. This epic is going to build on that.
The basic idea is that users will be able to upload configuration files that have specific "rules" (initially just simple code expressions (e.g. "a > 5.0 || a < 1.0")), and be notified when they are triggered.
Users should also be able to subscribe to other users configurations or rules.
Stakeholders
Product Stakeholder: TBD
Software Stakeholder: @bracyw @suryatho
Reference Users: @jr1221
User Story
As a embedded engineer, I want to be able to monitor values automatically, so that I can free up my focus during test days.
Success Metrics
- Jack and embedded team understand how to create and use rules.
- Rules are proven reliable.
- Rules can be shared.
Rollout Plan
All of the above should be kept in mind while building. But the main focus is working rules, and the ability to change and download current rules. Sharing is not the top priority.
Out of Scope
Persisting rules in the database. Persistence if any should be done client side for simplicity. Adding database schema to support the rules can be done later.
Background / Context
See overview, may add more detail later.
Acceptance Criteria & Mock-ups
In progress.
Tickets (see below)
Sub-issues
Metadata
Metadata
Assignees
Labels
Type
Projects
Status