documentation/content/applications/sales/crm/pipeline/lost_opportunities.rst
Antoine Vandevenne (anv) 6f125de01b [MOV] content/*: move resource files into their related page's directory
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

closes odoo/documentation#2006

Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-05-19 11:33:49 +02:00

79 lines
2.2 KiB
ReStructuredText

=========================
Manage lost opportunities
=========================
While working with your opportunities, you might lose some of them. You
will want to keep track of the reasons you lost them and also which ways
Odoo can help you recover them in the future.
Mark a lead as lost
===================
While in your pipeline, select any opportunity you want and you will see
a *Mark Lost* button.
You can then select an existing *Lost Reason* or create a new one
right there.
.. image:: lost_opportunities/lost_opportunities01.png
:align: center
Manage & create lost reasons
----------------------------
You will find your *Lost Reasons* under :menuselection:`Configuration --> Lost Reasons`.
You can select & rename any of them as well as create a new one from
there.
Retrieve lost opportunities
===========================
To retrieve lost opportunities and do actions on them (send an email,
make a feedback call, etc.), select the *Lost* filter in the search
bar.
.. image:: lost_opportunities/lost_opportunities02.png
:align: center
You will then see all your lost opportunities.
If you want to refine them further, you can add a filter on the *Lost
Reason*.
For Example, *Too Expensive*.
.. image:: lost_opportunities/lost_opportunities03.png
:align: center
Restore lost opportunities
==========================
From the Kanban view with the filter(s) in place, you can select any
opportunity you wish and work on it as usual. You can also restore it by
clicking on *Archived*.
.. image:: lost_opportunities/lost_opportunities04.png
:align: center
You can also restore items in batch from the Kanban view when they
belong to the same stage. Select *Restore Records* in the column
options. You can also archive the same way.
.. image:: lost_opportunities/lost_opportunities05.png
:align: center
To select specific opportunities, you should switch to the list view.
.. image:: lost_opportunities/lost_opportunities06.png
:align: center
Then you can select as many or all opportunities and select the actions
you want to take.
.. image:: lost_opportunities/lost_opportunities07.png
:align: center
.. seealso::
* :doc:`../performance/win_loss`