mantisbt:reporting_via_email
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
mantisbt:reporting_via_email [2007/04/14 05:51] – break up into logical unit and add notes aristedes | mantisbt:reporting_via_email [2013/12/26 13:05] (current) – Remove v* and p* bad words. vboctor | ||
---|---|---|---|
Line 7: | Line 7: | ||
* Making sure that users don't spoof the email FROM address to impersonate other users. | * Making sure that users don't spoof the email FROM address to impersonate other users. | ||
* Support different types of email formats and protocols (e.g. POP3). | * Support different types of email formats and protocols (e.g. POP3). | ||
- | * Making sure a company keeps control on the issues in their bug tracker (i.e. make sure no one can report a single issue that has viagra | + | * Making sure a company keeps control on the issues in their bug tracker (i.e. make sure no one can report a single issue that has spam links). |
+ | __giallu__ | ||
+ | |||
+ | '' | ||
===== Brainstorming ===== | ===== Brainstorming ===== | ||
Line 24: | Line 27: | ||
* Support for one email account per project or one for all projects. (//Ari Maniatis// I don't think this is needed | * Support for one email account per project or one for all projects. (//Ari Maniatis// I don't think this is needed | ||
+ | __giallu__ | ||
+ | |||
+ | '' | ||
===== Annotating tasks (meta-data) ===== | ===== Annotating tasks (meta-data) ===== | ||
Line 35: | Line 41: | ||
* project.category@bugs.mantisbt.org - creates a new bug in that project and category | * project.category@bugs.mantisbt.org - creates a new bug in that project and category | ||
* substitute space for underscore character appearing in name, e.g., Feature_Requests becomes " | * substitute space for underscore character appearing in name, e.g., Feature_Requests becomes " | ||
+ | |||
//Ari Maniatis:// | //Ari Maniatis:// | ||
I don't believe the above is particularly important. The main use for email submission is for customers who can't be expected to use a task tracking system, particularly when the tasks are system admin or sales requests. If the customer/ | I don't believe the above is particularly important. The main use for email submission is for customers who can't be expected to use a task tracking system, particularly when the tasks are system admin or sales requests. If the customer/ | ||
- | If automated collection of this metadata is important, I'd suggest a template block at the top of the incoming email rather than trying to overload the email address with meaning: | + | If automated collection of this metadata is important, I'd suggest a template block at the top of the incoming email rather than trying to overload the email address with meaning. In fact, even better would be to follow the existing Bugzilla format. It has been well thought through and the compatibility would be useful. |
- | '' | + | http:// |
- | '' | + | |
- | '' | + | __giallu__ |
+ | |||
+ | '' | ||
+ | Moreover, I wonder how you can expect a sysadmin to create all those email addresses just for mantis usage. IMHO everything should work with a single email address | ||
+ | '' | ||
===== Replying to existing tasks ===== | ===== Replying to existing tasks ===== | ||
Line 56: | Line 67: | ||
'' | '' | ||
Naturally we'd need to look beyond " | Naturally we'd need to look beyond " | ||
+ | |||
+ | __giallu__ | ||
+ | '' | ||
* If a user replies to a notification related to an issue, then the new part in the reply should be added as a note. Inline replies are not supported. | * If a user replies to a notification related to an issue, then the new part in the reply should be added as a note. Inline replies are not supported. |
mantisbt/reporting_via_email.txt · Last modified: 2013/12/26 13:05 by vboctor