You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
71 lines
3.4 KiB
71 lines
3.4 KiB
You need to define a view with the tag <timeline> as base element. These are
|
|
the possible attributes for the tag:
|
|
|
|
* date_start (required): it defines the name of the field of type date that
|
|
contains the start of the event.
|
|
* date_stop (optional): it defines the name of the field of type date that
|
|
contains the end of the event. The date_stop can be equal to the attribute
|
|
date_start to display events has 'point' on the Timeline (instantaneous event)
|
|
* date_delay (optional): it defines the name of the field of type float/integer
|
|
that contain the duration in hours of the event, default = 1
|
|
* default_group_by (required): it defines the name of the field that will be
|
|
taken as default group by when accessing the view or when no other group by
|
|
is selected.
|
|
* zoomKey (optional): Specifies whether the Timeline is only zoomed when an
|
|
additional key is down. Available values are '' (does not apply), 'altKey',
|
|
'ctrlKey', or 'metaKey'. Set this option if you want to be able to use the
|
|
scroll to navigate vertically on views with a lot of events.
|
|
* mode (optional): Specifies the initial visible window. Available values are:
|
|
'day' to display the current day, 'week', 'month' and 'fit'.
|
|
Default value is 'fit' to adjust the visible window such that it fits all items
|
|
* event_open_popup (optional): when set to true, it allows to edit the events
|
|
in a popup. If not (default value), the record is edited changing to form
|
|
view.
|
|
* colors (optional): it allows to set certain specific colors if the expressed
|
|
condition (JS syntax) is met.
|
|
* dependency_arrow (optional): set this attribute to a x2many field to draw
|
|
arrows between the records referenced in the x2many field.
|
|
|
|
Optionally you can declare a custom template, which will be used to render the
|
|
timeline items. You have to name the template 'timeline-item'.
|
|
These are the variables available in template rendering:
|
|
|
|
* ``record``: to access the fields values selected in the timeline definition.
|
|
* ``field_utils``: used to format and parse values (see available functions in ``web.field_utils``).
|
|
|
|
You also need to declare the view in an action window of the involved model.
|
|
|
|
Example:
|
|
|
|
.. code-block:: xml
|
|
|
|
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<record id="view_task_timeline" model="ir.ui.view">
|
|
<field name="model">project.task</field>
|
|
<field name="type">timeline</field>
|
|
<field name="arch" type="xml">
|
|
<timeline date_start="date_start"
|
|
date_stop="date_end"
|
|
string="Tasks"
|
|
default_group_by="user_id"
|
|
event_open_popup="true"
|
|
zoomKey="ctrlKey"
|
|
colors="#ec7063:user_id == false;#2ecb71:kanban_state=='done';"
|
|
dependency_arrow="task_dependency_ids">
|
|
<field name="user_id"/>
|
|
<templates>
|
|
<div t-name="timeline-item">
|
|
<div t-esc="record.display_name"/>
|
|
Assigned to:
|
|
<span t-esc="record.user_id[1]"/>
|
|
</div>
|
|
</templates>
|
|
</timeline>
|
|
</field>
|
|
</record>
|
|
|
|
<record id="project.action_view_task" model="ir.actions.act_window">
|
|
<field name="view_mode">kanban,tree,form,calendar,gantt,timeline,graph</field>
|
|
</record>
|
|
</odoo>
|