Implement Match State #2
Labels
No labels
help wanted
question
Subsystem/Backend
Subsystem/Frontend
Subsystem/Mail
Kind
Breaking
Kind
Bug
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Security
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: c3lf/c3lf-system-3#2
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A match object will recieve a status representing the current state of a match.
states:
possible, verified, notified, collected, shipable, shipped
transitions:
on start: possible (a match is created as possible match)
possible -> verified (successfully reviewed (maybe by looking at an item or photo))
possible -> /dev/null (review unsuccessful (this is not the item you are looking for!))
verified -> notified (send mail to user, either to fetch item or send address)
notified -> collected (if item was picked up)
notified -> shipable (if item has to be sent)
shipable -> shipped (if item is shipped)
A Lost Request can have multiple possible matches with distinct items.