Content
View differences
Updated by Hagen Mahnke 11 months ago
**As** an OpenProject administrator
**I want to** create and manage email inboxes in the administration
**so that** I can do this without server access.
**Acceptance criteria**
* An index for **incoming In case there is an email configurations** exists
* Each entry contains
* inbox configured in the name
* [configuration files](https://www.openproject.org/docs/installation-and-operations/configuration/incoming-emails/) the recipient email address
* an edit button
* administration provides a delete button
* A button user interface for adding a new **incoming email configuration** exists
* A create/edit view for an **incoming email configuration** contains fields for the settings.
* Name Email address
* Recipient email address Server settings
* IMAP configuration
Security options
* Host
* Port
* SSL/TLS
* default 'true'
* 'false (not recommended)'
* SSL verification
* default 'true'
* 'false'
* Username
* Password
* Poll interval (in seconds)
* default 600
* Folder
* default 'INBOX'
* Move to folder on success (OPTIONAL)
* Move to folder on failure (OPTIONAL)
* Work package configuration
* Project
* Category
* Priority
* Status
* Version
* Type
* Assign to
* Unknown user
* default 'Ignore'
* 'Accept as anonymous user'
* 'Create a user'
* No permission check
* default 'false'
* 'true' (should be mapped to 1 for the backend)
* Allow override
* Explanation: 'A comma separated list of attributes that can be overridden in the email even though a value was specified here.'
* It's also still It is possible to configure an inbox through ENV variables, see [https://www.openproject.org/docs/installation-and-operations/configuration/incoming-emails/](https://www.openproject.org/docs/installation-and-operations/configuration/incoming-emails/)
* If any of these ENV variables are set, display an **incoming create multiple email configuration** with those values in the first position in the list
* ##65268
inboxes.
**Technical notes**
* <br>
**Permissions and visibility considerations**
* _Only admins can manage the email inboxes_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* Button to test the connection
* Processing of incoming emails that are sent to the inboxes.
**I want to** create and manage email inboxes in the administration
**so that** I can do this without server access.
**Acceptance criteria**
* An index for **incoming
* Each entry contains
*
*
* an edit button
*
* A button
* A create/edit view for an **incoming email configuration** contains fields for
* Name
* Recipient email address
* IMAP configuration
* Port
* SSL/TLS
* default 'true'
* 'false (not recommended)'
* SSL verification
* default 'true'
* 'false'
* Username
* default 600
* Folder
* default 'INBOX'
* Move to folder on success (OPTIONAL)
* Move to folder on failure (OPTIONAL)
* Work package configuration
* Project
* Category
* Priority
* Status
* Version
* Type
* Assign to
* Unknown user
* default 'Ignore'
* 'Accept as anonymous user'
* 'Create a user'
* No permission check
* default 'false'
* 'true' (should be mapped to 1 for the backend)
* Allow override
* Explanation: 'A comma separated list of attributes that can be overridden in the email even though a value was specified here.'
* It's also still
* If any of these ENV variables are set, display an **incoming
* ##65268
* <br>
**Permissions and visibility considerations**
* _Only admins can manage the email inboxes_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* Button to test the connection
* Processing of incoming emails that are sent to the inboxes.