Thibault Delavallée
1aa0f9a4db
It is simpler to have data split by main model or application like we already do for models and views. It allows to easily have an overview of data a module holds. As we will work on mail related data like adding activities or tweaking subtypes and templates, having them all in a single file and not lost between other data helps finding and working with it. This commit only moves code. No functional change should occur.
31 lines
993 B
XML
31 lines
993 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<data>
|
|
|
|
<!-- Standard stages for Maintenance Request -->
|
|
<record id="stage_0" model="maintenance.stage">
|
|
<field name="name">New Request</field>
|
|
<field name="sequence" eval="1" />
|
|
<field name="fold" eval="False" />
|
|
</record>
|
|
<record id="stage_1" model="maintenance.stage">
|
|
<field name="name">In Progress</field>
|
|
<field name="sequence" eval="2" />
|
|
<field name="fold" eval="False" />
|
|
</record>
|
|
<record id="stage_3" model="maintenance.stage">
|
|
<field name="name">Repaired</field>
|
|
<field name="sequence" eval="3" />
|
|
<field name="fold" eval="True" />
|
|
<field name="done" eval="True" />
|
|
</record>
|
|
<record id="stage_4" model="maintenance.stage">
|
|
<field name="name">Scrap</field>
|
|
<field name="sequence" eval="4" />
|
|
<field name="fold" eval="True" />
|
|
<field name="done" eval="True" />
|
|
</record>
|
|
|
|
</data>
|
|
</odoo>
|