Content
View differences
Updated by Wieland Lindenthal over 5 years ago
### User Problem
#### User
Basically everybody on a project.
#### Problem
Hard to find and use the inbound email feature correctly.
#### Pain
You cannot find how to use it, even if you search for it on Google.
### Solution
* [ ] Have some very basic beginner instructions in the footer of every notification mail that we sent. "Reply to this mail to add a comment. Want to update more attrigutes? Check out these instructions (link)"
* [ ] Use speaking mail addresses. The current "notification+<instance-identifier>@instancename.openproject.com" is hard to remember. So it is pretty impossible to simply write an email to create a WP when you are in the street with your mobile. You'd first need to copy that mail address. Actually, I don't understand why we need an identifier before the @-sign if the instance is identifiable by its (sub)domain.
* [ ] Reply with feedback, if sending failed. Currently you don't get any info when you send your email from the wrong email address. This happens so easily. Everybody in a working environment has at least two mail addresses on their mobile phone: work and private. It is easy to mess them up. You send a mail and nothing happens. I send a mail once into nirvana and lose trust in the system forever. Further you don't get feedback if you used the attributes keys and values wrong. The mail goes through and accepts what it understands. However, the user needs feedback that some attribute values were not understood so that the user has the chance to correct them.
* [ ] Remove e-Mail signatures. Make an effort to remove those lines.
#### User
Basically everybody on a project.
#### Problem
Hard to find and use the inbound email feature correctly.
#### Pain
You cannot find how to use it, even if you search for it on Google.
### Solution
* [ ] Have some very basic beginner instructions in the footer of every notification mail that we sent. "Reply to this mail to add a comment. Want to update more attrigutes? Check out these instructions (link)"
* [ ] Use speaking mail addresses. The current "notification+<instance-identifier>@instancename.openproject.com" is hard to remember. So it is pretty impossible to simply write an email to create a WP when you are in the street with your mobile. You'd first need to copy that mail address. Actually, I don't understand why we need an identifier before the @-sign if the instance is identifiable by its (sub)domain.
* [ ] Reply with feedback, if sending failed. Currently you don't get any info when you send your email from the wrong email address. This happens so easily. Everybody in a working environment has at least two mail addresses on their mobile phone: work and private. It is easy to mess them up. You send a mail and nothing happens. I send a mail once into nirvana and lose trust in the system forever. Further you don't get feedback if you used the attributes keys and values wrong. The mail goes through and accepts what it understands. However, the user needs feedback that some attribute values were not understood so that the user has the chance to correct them.
* [ ] Remove e-Mail signatures. Make an effort to remove those lines.