Closed
Bug 896044
Opened 12 years ago
Closed 11 years ago
Add an API endpoint to receive email message for Communication Dashboard
Categories
(Marketplace Graveyard :: API, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
2013-08-20
People
(Reporter: cvan, Assigned: ashish_d)
References
Details
(Whiteboard: [qa-])
POST /api/v1/comm/email/
As described in bug 881799 comment 4, we need an API endpoint that will accept the contents of an email message. In this endpoint, we should then pass the contents of the email message to a celery task which will parse and then save the thread/note in the database (see bug 879412).
Updated•12 years ago
|
Priority: -- → P3
Reporter | ||
Comment 1•12 years ago
|
||
Assignee | ||
Comment 2•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•11 years ago
|
Whiteboard: [qa-]
Target Milestone: --- → 2013-08-08
Reporter | ||
Comment 3•11 years ago
|
||
Reopening to address bug 902646 comment 3.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: 2013-08-06 → 2013-08-20
Reporter | ||
Comment 4•11 years ago
|
||
https://github.com/mozilla/zamboni/commit/35a7884
Thanks, Ashish!
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•