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
88 lines
2.8 KiB
ReStructuredText
88 lines
2.8 KiB
ReStructuredText
===========================
|
|
Visualize a project's tasks
|
|
===========================
|
|
|
|
In day to day business, your company might struggle due to the important
|
|
amount of tasks to fulfill. Those tasks already are complex enough.
|
|
Having to remember them all and follow up on them can be a burden.
|
|
Luckily, Odoo enables you to efficiently visualize and organize the
|
|
different tasks you have to cope with.
|
|
|
|
Create a task
|
|
=============
|
|
|
|
While in the project app, select an existing project or create a new
|
|
one.
|
|
|
|
In the project, create a new task.
|
|
|
|
.. image:: media/visualization01.png
|
|
:align: center
|
|
|
|
In that task you can then assigned it to the right person, add tags, a
|
|
deadline, descriptions… and anything else you might need for that task.
|
|
|
|
.. image:: media/visualization02.png
|
|
:align: center
|
|
|
|
View your tasks with the Kanban view
|
|
====================================
|
|
|
|
Once you created several tasks, they can be managed and followed up
|
|
thanks to the Kanban view.
|
|
|
|
The Kanban view is a post-it like view, divided in different stages. It
|
|
enables you to have a clear view on the stages your tasks are in and
|
|
which one have the higher priorities.
|
|
|
|
The Kanban view is the default view when accessing a project, but if you
|
|
are on another view, you can go back to it any time by clicking the
|
|
kanban view logo in the upper right corner
|
|
|
|
.. image:: media/visualization03.png
|
|
:align: center
|
|
|
|
You can also notify your colleagues about the status of a task right
|
|
from the Kanban view by using the little dot, it will notify follower of
|
|
the task and indicate if the task is ready.
|
|
|
|
.. image:: media/visualization04.png
|
|
:align: center
|
|
|
|
Sort tasks in your Kanban view
|
|
==============================
|
|
|
|
Tasks are ordered by priority, which you can give by clicking on the
|
|
star next to the clock and then by sequence, meaning if you manually
|
|
move them using drag & drop, they will be in that order and finally by
|
|
their ID linked to their creation date.
|
|
|
|
.. image:: media/visualization05.png
|
|
:align: center
|
|
|
|
Tasks that are past their deadline will appear in red in your Kanban
|
|
view.
|
|
|
|
.. note::
|
|
If you put a low priority task on top, when you go back to your
|
|
dashboard the next time, it will have moved back below the high priority
|
|
tasks.
|
|
|
|
Manage deadlines with the Calendar view
|
|
=======================================
|
|
|
|
You also have the option to switch from a Kanban view to a calendar
|
|
view, allowing you to see every deadline for every task that has a
|
|
deadline set easily in a single window.
|
|
|
|
Tasks are color coded to the employee they are assigned to and you can
|
|
filter deadlines by employees by selecting who's deadline you wish to
|
|
see.
|
|
|
|
.. image:: media/visualization06.png
|
|
:align: center
|
|
|
|
.. tip::
|
|
You can easily change the deadline from the Calendar view by
|
|
dragging and dropping the task to another case.
|