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
103 lines
3.0 KiB
ReStructuredText
103 lines
3.0 KiB
ReStructuredText
====================================
|
|
How to set up & configure a project?
|
|
====================================
|
|
|
|
Overview
|
|
========
|
|
|
|
Odoo Project allows you to manage a project together with your whole
|
|
team, and to communicate with any member for each project and task.
|
|
|
|
It works with projects containing tasks following customizable stages.
|
|
A project can be internal or customer-oriented. A task is something to
|
|
perform as part of a project. You will be able to give different tasks
|
|
to several employees working on this project.
|
|
|
|
Installing the Project module
|
|
=============================
|
|
|
|
Open the **Apps** module, search for **Project Management**, and click on
|
|
**Install**.
|
|
|
|
.. image:: media/setup01.png
|
|
:align: center
|
|
|
|
Creating a new project
|
|
======================
|
|
|
|
Open the **Project** application, and click on **Create**. From this window,
|
|
you can specify the name of the project and set up the privacy of the
|
|
project.
|
|
|
|
The privacy setting works as:
|
|
|
|
- **Customer Project**: visible in portal if the customer is a
|
|
follower.
|
|
|
|
- **All Employees**: employees see all tasks or issues.
|
|
|
|
- **Private Project**: followers can see only the followed tasks or
|
|
issues
|
|
|
|
You can also specify if the project is destined to a customer, or leave
|
|
the **Customer** field empty if not.
|
|
|
|
.. image:: media/setup02.png
|
|
:align: center
|
|
|
|
When you have entered all the required details, click on **Save**.
|
|
|
|
Manage your project's stages
|
|
============================
|
|
|
|
Add your project's stages
|
|
-------------------------
|
|
|
|
On your project's dashboard. Click on **# Tasks**.
|
|
|
|
.. image:: media/setup03.png
|
|
:align: center
|
|
|
|
In the new window, add a new column and name it according to the first
|
|
stage of your project, then add as many columns as there are stages in
|
|
your project.
|
|
|
|
.. image:: media/setup04.png
|
|
:align: center
|
|
|
|
For each stage, there are markers for the status of tasks within a
|
|
stage, that you can personalize to fit your needs.
|
|
|
|
Drag your mouse pointer over a stage name, and click on the appearing
|
|
bearing, and on the opening menu, click on **Edit**.
|
|
|
|
.. image:: media/setup05.png
|
|
:align: center
|
|
|
|
A new window will open. The color dots and star icon correspond to
|
|
customizable markers applied on tasks, making it easier to know what
|
|
task requires attention. You can give them any signification you like.
|
|
|
|
.. image:: media/setup06.png
|
|
:align: center
|
|
|
|
Click on **Save** when you are done.
|
|
|
|
Rearrange stages
|
|
----------------
|
|
|
|
You can easily personalize this view to better suit your business needs
|
|
by creating new columns. From the Kanban view of your project, you can
|
|
add stages by clicking on **Add new column**. If you want to rearrange
|
|
the order of your stages, you can easily do so by dragging and dropping
|
|
the column you want to move to the desired location. You can also fold
|
|
or unfold your stages by using the **Setting** icon on your desired stage.
|
|
|
|
.. image:: media/setup07.png
|
|
:align: center
|
|
|
|
.. seealso::
|
|
* :doc:`visualization`
|
|
* :doc:`collaboration`
|
|
* :doc:`time_record`
|