- Status Planned
- Percent Complete
- Task Type Feature Request
- Category Backend/Core
- Assigned To No-one
- Operating System All
- Severity Low
- Priority Very Low
- Reported Version 1.0 devel (github master)
- Due in Version 2.0
-
Due Date
Undecided
-
Votes
3
- H (29.10.2015)
- Jordan Mendler (25.01.2013)
- Col (25.01.2013)
- Private
Attached to Project: Flyspray - The bug killer!
Opened by Jordan Mendler - 17.01.2013
Last edited by Psychokiller1888 - 07.03.2015
Opened by Jordan Mendler - 17.01.2013
Last edited by Psychokiller1888 - 07.03.2015
FS#1819 - Communicate via email
Need to be able to email back and forth to communicate with flyspray. Ideally flyspray can be CC'ed on an email or can replay to a notification which would add the body and/or attachments to the thread. This goes back to reworking the way people interact with and view tickets
ID | Project | Summary | Priority | Severity | Assigned To | Progress | |
---|---|---|---|---|---|---|---|
1812 | Flyspray - The bug killer! | FS#1812 - Multiple email addresses | Very Low | Low |
I have already added this in my 0.9.9.7 version. Its not the best piece of coding I have ever written but works a treat.
It has made a massive difference for the organisation I work for, it now allows for non registered users to email in their support tasks and permits them to simply reply to the email sent back to them to add new comments to the task.
Doesn't handle attachments though.
Col,
Any way you could submit a patch?
Or better yet, if you could merge it into Git that would be even better
No problem, will try and get it done this weekend.
Col,
Never got the patch. Do you mind submitting it?
Jordan,
I have attached 2 files.
The file that I am currently using (cron.emailParser.php) gets called every minute via a cron job.
It is certainly not pretty code, but, for my purposes it works a treat.
The second file is a email parser script that I use in another project I have. I was planning on using this to replace the email parts of the other script as it handles attachments and generally is more bullet proof.
Hope this helps.
Regards
Col
TODOs for an Email2Flyspray create task/update task feature
Usage of Flyspray configuration and classes as far possible:
what methods do we implement to be sure the Email comes really from an authorized Flyspray user and is not faked? Checking PGP signatures or similiar comes to my mind.
Format for the users that Flyspray can analyze easy:
For example create a new task:
If the email subject contains only a html part and no text part, the html should be stripped from html tags first.
Before implementing this, there must be the "multiple email feature" done right, see FS#1812.
Maybe use existing rules (or parts of) of another bug tracker - bugzilla: https://www.bugzilla.org/docs/3.0/html/api/email_in.html
So not to reinvent the wheel..