8722ea902e
Since odoo/documentation#903, the guideline for the location of new resource (images, downloadable files, RST includes...) files is to place those inside the directory of the RST page that references them. For example, if `doc1.rst` has a reference to `image.png` and to `download.zip`, the file structure should look like this: ├── parent_doc/ │ └── doc1/ │ │ └── image.png │ │ └── download.zip │ └── doc1.rst │ └── doc2.rst ├── parent_doc.rst Before this commit, most of the resource files were still located inside 'media' directories holding all the resource files referenced by RST pages located at the same level as these directories. In the example above, a single 'media' directory would hold all the resource files referenced by both `doc1.rst` and `doc2.rst`. Doing so prevented us from figuring out easily which resource file was referenced by which RST page and, thus, lead to unused resource files piling up in the repository. It also made it more complicated to define codeowners regex rules because a team could not simply be assigned to `/some_page.*` but needed to be assigned to both `/some_page\.rst` and to the location of 'media'. In order to help new content writers figure out the guideline when taking examples from other RST pages, this commit retroactively applies the guideline to existing resource files and 'media' directories. The left-over resource files that are not referenced by any RST page are removed. task-2497965 Part-of: odoo/documentation#2068
39 lines
1.6 KiB
ReStructuredText
39 lines
1.6 KiB
ReStructuredText
==========================================
|
|
Create Project's Tasks from an Email Alias
|
|
==========================================
|
|
|
|
When you already have an email address that customers know from the top of their heads, changing
|
|
it is the last thing you want to do. Instead, link that address to your project and transform
|
|
those conversations into structured work. It automatically creates a task in the first stage
|
|
of a project.
|
|
|
|
Set up an incoming email server
|
|
===============================
|
|
|
|
| On the *Settings* application, enable *External Email Servers* and define the incoming email
|
|
alias you would like to use.
|
|
| **For more information**: :doc:`/applications/general/email_communication/email_servers`
|
|
|
|
Configure the email alias in your project
|
|
-----------------------------------------
|
|
|
|
| Now that you have the incoming email server set up, go to
|
|
:menuselection:`Project --> Configuration --> Projects --> Edit`. Under the *Emails* tab, define
|
|
the wanted email alias and choose the policy to receive a message.
|
|
| In addition, you can now directly set it when creating a new project.
|
|
|
|
.. image:: email_alias/email_project.png
|
|
:align: center
|
|
:alt: In the settings of your project, define the emails alias under the tab email in Odoo Project
|
|
|
|
.. important::
|
|
All the recipients of the email (To/Cc/Bcc) are automatically added as followers of the task.
|
|
|
|
The email can be seen under the name of your project on the dashboard.
|
|
|
|
.. image:: email_alias/email_dashboard_project.png
|
|
:align: center
|
|
:height: 300
|
|
:alt: View of the email alias chosen on the dashboard view in Odoo Project
|
|
|