e3fee2cf46
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
79 lines
2.1 KiB
ReStructuredText
79 lines
2.1 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:: media/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:: media/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:: media/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:: media/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:: media/lost_opportunities05.png
|
|
:align: center
|
|
|
|
To select specific opportunities, you should switch to the list view.
|
|
|
|
.. image:: media/lost_opportunities06.png
|
|
:align: center
|
|
|
|
Then you can select as many or all opportunities and select the actions
|
|
you want to take.
|
|
|
|
.. image:: media/lost_opportunities07.png
|
|
:align: center
|
|
|
|
.. seealso::
|
|
* :doc:`../performance/win_loss`
|