Audric Onockx (auon)
85e9290711
*=hr_timesheet,project,sale_project,sale_timesheet Currently, the configuration of the recurrence is quite complete and allows a lot of flexibility, but it is costly in terms of implementation as it requires a lot of fields. The goal of this task is thus to simplify this implementation. In addition, a lot of people are complaining that tasks are only generated when the recurrence date is reached, as it doesn't allow to anticipate the planning of field service tasks. In this task, we are thus going to immediately generate a new task once the previous one is marked as done. Concretely, we: - describe a recurrence in terms of "once every n day/week/month/year for ever/until a date" and delete all fields that don't fit into it. - remove the cron. The new occurrence is created when marking the last task as done, and copied from the latter. Deleting the last task deletes the recurrence. The recurrence fields stay useful, as they form a delta t that will be added to deadline/planned dates fields to get the new values. - use an boolean icon button to activate recurrence, and place it at the end of deadline field's line. The recurrence fields appear on the next line. - delete in the form: the div explaining when the next tasks will be created and the header to choose how to save the changes in the recurrence. task-3084945 closes odoo/odoo#112764 Related: odoo/upgrade#4343 Related: odoo/enterprise#37114 Signed-off-by: Xavier Bol (xbo) <xbo@odoo.com>
12 lines
457 B
XML
12 lines
457 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo noupdate="1">
|
|
<record id="ir_cron_rating_project" model="ir.cron">
|
|
<field name="name">Project: Send rating</field>
|
|
<field name="model_id" ref="project.model_project_project"/>
|
|
<field name="state">code</field>
|
|
<field name="code">model._send_rating_all()</field>
|
|
<field name="interval_type">days</field>
|
|
<field name="numbercall">-1</field>
|
|
</record>
|
|
</odoo>
|