Search 1.9 billion lines of Odoo code on GitHub

fieldservice_size

Author: Brian McMaster, Odoo Community Association (OCA)
License: AGPL-3
Branch: 15.0_MIG_fieldservice_size
Repository: ursais/field-service
Dependencies: fieldservice, and uom
Languages: HTML (374, 36.7%), PO File (280, 27.5%), Python (174, 17.1%), XML (97, 9.5%), and reStructuredText (93, 9.1%)
Other branches: 12.0, 12.0-FIX-fieldservice, 12.0-FIX-unble_to_set_territory, 12.0-IMP-field_service_location, 12.0-IMP-fieldservice_google_map, 12.0-add-fsm_loc_builder_analytic, 12.0-add-fsm_loc_builder_stock, 12.0-add-route-get-schedule, 12.0-ccu-RC13, 12.0-dr-utc-filters, 12.0-dr-utc-fix, 12.0-fix-fieldservice_crm, 12.0-fix-fieldservice_route, 12.0-fix-fieldservice_route_vehicle, 12.0-fix-fsm_invoice_double_entry, 12.0-fix-fsm_order_utc_filter, 12.0-fix-issue-524, 12.0-fix-stock-upgrade, 12.0-imp-art_12.1, 12.0-imp-fieldservice_route, 12.0-imp-fieldservice_route_stock, 12.0-imp-fieldservice_substatus_notifications, 12.0-imp-force-create-fsm, 12.0-imp-fsm_computed_fields_split_method, 12.0-imp-fsm_isp_acc_noupdate, 12.0-imp-fsm_isp_acc_timesheet_contractor_costs, 12.0-imp-fsm_maintenance_convert_equipment, 12.0-imp-fsm_sale_team_template, 12.0-imp-fsm_substatus_notifications, 12.0-imp-fsm_vehicle_sale_require_vehicle, 12.0-orr, 12.0_art_fsm_0814, 14-dr-copier, 14-dr-fieldservice-multicompany, 14.0, 14.0-FIX-Fieldservice_date_start, 14.0-IMP-fieldservice_account, 14.0-IMP-scheduled_date_start, 14.0-MIG-fiedservice_geoengine, 14.0-MIG-fieldservice_location_builder, 14.0-fix-fieldservice-calendar_event, 14.0-fix-fsm_location_loading_issue, 14.0-go_live, 14.0-imp-dont_filter_skill, 14.0-mig-fieldservice_stock_request, 14.0-sm, 14_fieldservice_stock_account, 15-dr-copier, 15.0, 15.0-MIG-fieldservice_maintenance, 15.0-MIG-fieldservice_vehicle, 15.0-MIG-fieldservice_vehicle_stock, 15.0_MIG_fieldservice_account_payment, 15.0_MIG_fieldservice_distribution, 15.0_MIG_fs_isp_account, 15.0_mig_fieldservice_delivery, 15.0_mig_fieldservice_google_map, 15.0_mig_fieldservice_sale, IMP-12.0-fieldservice, KUDU/14.0.1.0.0, KUDU/14.0.2.0.2, KUDU/14.0.2.0.6, KUDU/14.0.2.0.7, KUDU/14.0.2.0.9, ORR/14.0.4.0.0, ORR/14.0.7.0.0, ORR/14.0.8.0.0, ORR/14.0.9.0.0, UMT/14.0, art/12.0-RC1, art/12.01, art/12.1-RC1, art/12.1-RC2, ccu/12.0-RC10, ccu/12.0-RC11, ccu/12.0-RC12, ccu/12.0-RC13, ccu/12.0-RC14, ccu/12.0-RC15, ccu/12.0-RC16, ccu/12.0-RC17, ccu/12.0-RC18, ccu/12.0-RC19, ccu/12.0-RC20, ccu/12.0-RC8, ccu/12.0-RC9, dr/14.0, fsm/15.0.0.1, pvm/12.16-RC5, pvm/12.17-RC1, pvm/12.17-RC2, pvm/12.17-RC4, pvm/12.17-RC5, pvm/12.18-RC1, pvm/12.18-RC2, pvm/12.19-RC1, pvm/12.20-RC1, pvm/12.21-RC1, pvm/12.22-RC1, pvm/12.22-RC2, pvm/12.22-RC3, pvm/12.22-RC5, pvm/12.22-RC6, pvm/12.22-RC7, pvm/12.23-RC1, pvm/12.23-RC2, pvm/12.24-RC1, pvm/12.25-RC1, pvm/12.25-RC2, pvm/12.25-RC3, pvm/12.25-RC4, pvm/12.25-RC5, pvm/12.26-RC1, pvm/12.26-RC2, pvm/12.27-RC1, pvm/12.28-RC1, pvm/12.28-RC2, pvm/12.29-RC1, pvm/12.29-RC2, pvm/12.29-RC3, pvm/12.30-RC1, pvm/12.30-RC2, pvm/12.32-RC2, pvm/12.33-RC1, pvm/14.0.1.0.0-RC2, pvm/14.0.1.0.0-RC2-max, pvm/14.0.1.0.1-RC1, pvm/14.0.1.16.0, pvm/14.0.1.17.0, revert-38-12.0, and umt/14.24.0.0
Other repositories: ACVIT/field-service, Ahmed9914/field-service, Change2improve/field-service, ERPLibre/field-service, Escodoo/field-service, Gabinete-Digital/field-service, Ingeos/field-service, K-schumac/field-service, LevelPrime/field-service, MYRCONSULTING/field-service, NeatNerdPrime/field-service, OCA-MUK/field-service, OCA/field-service, SerpentConsultingServices/field-service, agranadosb/field-service, agranadosb55199/field-service, akretion/field-service, amardimiaty/field-service, brian10048/field-service, codentsoftware/field-service, coopiteasy/field-service, diegobgl/field-service, dreispt/field-service, hippe-67/field-service, hpatelserpentcs/field-service, jmm20/field-service, marcelsavegnago/field-service, meganphan/field-service, murtuzasaleh/field-service, patrickrwilson/field-service, pdyharshad/field-service, popsolutions/field-service, robertsvx27/field-service, sanube/field-service, sendalpegat/field-service, tymiles003/field-service, valmarnet/field-service, and yassirgourram/field-service

<h1 class="title">Field Service Sizes</h1> <p><a class="reference external" href="https://odoo-community.org/page/development-status"><img alt="Beta" src="https://img.shields.io/badge/maturity-Beta-yellow.png" /></a> <a class="reference external" href="http://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.png" /></a> <a class="reference external" href="https://github.com/OCA/field-service/tree/14.0/fieldservice_size"><img alt="OCA/field-service" src="https://img.shields.io/badge/github-OCA%2Ffield--service-lightgray.png?logo=github" /></a> <a class="reference external" href="https://translation.odoo-community.org/projects/field-service-14-0/field-service-14-0-fieldservice_size"><img alt="Translate me on Weblate" src="https://img.shields.io/badge/weblate-Translate%20me-F47D42.png" /></a> <a class="reference external" href="https://runbot.odoo-community.org/runbot/264/14.0"><img alt="Try me on Runbot" src="https://img.shields.io/badge/runbot-Try%20me-875A7B.png" /></a></p> <p>Some field service operations may need to track the size of a field service location and its orders.</p> <p>Examples of sizes might be: - Area measure of a location - Count of service or maintenance items at a location</p> <p>Once established, sizes can be useful for route capacity planning, time estimation for orders, or for planning stock and inventory moves.</p> <p>This module allows you to establish sizes for your field service orders. Multiple sizes can be configured and established for a location. Order size will be updated based on its location and order type.</p> <p><strong>Table of contents</strong></p> <div class="contents local topic" id="contents"> <ul class="simple"> <li><a class="reference internal" href="#configuration" id="id1">Configuration</a></li> <li><a class="reference internal" href="#usage" id="id2">Usage</a></li> <li><a class="reference internal" href="#known-issues-roadmap" id="id3">Known issues / Roadmap</a></li> <li><a class="reference internal" href="#bug-tracker" id="id4">Bug Tracker</a></li> <li><a class="reference internal" href="#credits" id="id5">Credits</a><ul> <li><a class="reference internal" href="#authors" id="id6">Authors</a></li> <li><a class="reference internal" href="#contributors" id="id7">Contributors</a></li> <li><a class="reference internal" href="#maintainers" id="id8">Maintainers</a></li> </ul> </li> </ul> </div> <a name="configuration"></a> <h2><a class="toc-backref" href="#id1">Configuration</a></h2> <p>To configure field service sizes, go to Configuration &gt; Sizes.</p> <p>Set the size name, type of orders to which the size will apply, and unit of measure for the size. If this size is the default size to be used for orders of the designated type, select the option for 'Is Order Size'.</p> <a name="usage"></a> <h2><a class="toc-backref" href="#id2">Usage</a></h2> <p>## Enter sizes for field service locations. Go to Master Data &gt; Locations</p> <ol class="arabic simple"> <li>Select or create a location.</li> <li>Go to the Sizes tab.</li> <li>Select a Size. Enter the value for the size.</li> </ol> <p>## Use Order Sizes</p> <ol class="arabic simple"> <li>Select or create a field service order.</li> <li>Set a location on the order.</li> <li>Set a type on the order.</li> <li>The size value will update to the location's size value of the order type's default size.</li> </ol> <a name="known-issues-roadmap"></a> <h2><a class="toc-backref" href="#id3">Known issues / Roadmap</a></h2> <p>The roadmap of the Field Service application is documented on <a class="reference external" href="https://github.com/OCA/field-service/issues/1">Github</a>.</p> <a name="bug-tracker"></a> <h2><a class="toc-backref" href="#id4">Bug Tracker</a></h2> <p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/field-service/issues">GitHub Issues</a>. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed <a class="reference external" href="https://github.com/OCA/field-service/issues/new?body=module:%20fieldservice_size%0Aversion:%2014.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**">feedback</a>.</p> <p>Do not contact contributors directly about support or help with technical issues.</p> <a name="credits"></a> <h2><a class="toc-backref" href="#id5">Credits</a></h2> <a name="authors"></a> <h3><a class="toc-backref" href="#id6">Authors</a></h3> <ul class="simple"> <li>Brian McMaster</li> </ul> <a name="contributors"></a> <h3><a class="toc-backref" href="#id7">Contributors</a></h3> <ul class="simple"> <li>Brian McMaster &lt;<a class="reference external" href="mailto:brian&#64;mcmpest.com">brian&#64;mcmpest.com</a>&gt;</li> </ul> <a name="maintainers"></a> <h3><a class="toc-backref" href="#id8">Maintainers</a></h3> <p>This module is maintained by the OCA.</p> <a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" /></a> <p>OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.</p> <p>Current <a class="reference external" href="https://odoo-community.org/page/maintainer-role">maintainer</a>:</p> <p><a class="reference external" href="https://github.com/brian10048"><img alt="brian10048" src="https://github.com/brian10048.png?size=40px" /></a></p> <p>This module is part of the <a class="reference external" href="https://github.com/OCA/field-service/tree/14.0/fieldservice_size">OCA/field-service</a> project on GitHub.</p> <p>You are welcome to contribute. To learn how please visit <a class="reference external" href="https://odoo-community.org/page/Contribute">https://odoo-community.org/page/Contribute</a>.</p>