| Age | Commit message (Collapse) | Author |
|---|
|
For the graph views based on reporting models (e.g sale.report), click
on a group in the chart redirects the user to an "empty" list view. Here
we use the attribute disable_linking to avoid that redirection for those
views.
Task ID: 2336960
closes odoo/odoo#57602
X-original-commit: e5311141d575bc2c28e7ee536c2c63fc9b20e370
Related: odoo/enterprise#13183
Signed-off-by: Aaron Bohy (aab) <aab@odoo.com>
|
|
The purpose of this commit is to enable sample data on various graph and
pivot views.
Task ID: 2319606
closes odoo/odoo#55917
Related: odoo/enterprise#12415
Signed-off-by: Mathieu Duckerts-Antoine <Polymorphe57@users.noreply.github.com>
|
|
The purpose of this commit is to add many action helper messages.
TaskID: 2311486
|
|
The purpose of this commit is to enable sample data in various
graph views.
TaskID: 2311486
|
|
PURPOSE
=======
The task aims at adding date filters across various modules in preparation
for the 'time range' feature rework on task 2245719
https://www.odoo.com/web#id=2245719&action=327&model=project.task&view_type=form&cids=1&menu_id=4720
SPECIFICATION
=============
New date filters to compensate the deprecated time ranges feature:
See task's pad for the complete details
closes odoo/odoo#52398
Taskid: 2263661
Related: odoo/enterprise#10938
Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
|
|
|
|
(beaa30a3d1843de43a45f419bfbc1bfa7613a920)
This commit merges the following models
* account.invoice and account.move
* account.invoice.line and account.move.line
* account.voucher and account.move
* account.voucher.line and account.move.line
It was the opportunity for a big cleanup of the code, so it also restructures the whole account module, its different models/fields, the tests etc. for a better world and a better code readability.
==== Rationale ====
The rationale of this huge change is that we want journal entries / invoices to be easily edited, and changes reflected in the other model. It's a HUGE feature and very strategic for the fiduciary companies. For example, changing the account of a journal entry needs to be automatically reflected on the related invoice.
The same reasoning applies to sale/purchase vouchers.
==== Changes made in features =====
When creating an invoice, you are now creating a journal entry directly.
--> The object account.invoice no longer exists.
In the same fashion when creating an invoice line, you're now adding journal items directly in the journal entry representing the invoice. If this invoice line has some tax, it may create additional journal items as well.
--> The models account.invoice.line & account.invoice.tax no longer exist
Identically, when creating a sale/purchase receipt with its lines, you are now creating a journal entry directly and there's no more usability difference between encoding a receipt or an invoice.
--> The object account.voucher no longer exists.
--> The object account.voucher.line no longer exists.
--> The whole account_voucher module no longer exists.
Positive side-effects coming from these changes are
* draft invoices/bills/sale or purchase receipts now create a draft accounting entry. Validate these objects now simply post its journal entry. That means that draft invoices/bills/sale or purchase receipt can straightforwardly be included in reporting or budgets.
* opening a journal entry in form view will now always open the correct view: if it's a sale/purchase journal entry we will have a customer invoice/vendor bill view or a sale/purchase receipt view, whatever the menu we're coming from.
* code & business logic simplification. It is also condensed in a single place instead of being partially duplicated on invoices, vouchers and journal entries.
There should be no feature loss, except the one allowing to group multiple journal items together based on the same product during the invoice validation.
==== Changes made in models =====
* account.invoice: model removed. Instead, now use account.move with following mapping
field (account.invoice) field (account.move)
----------------------- --------------------
name invoice_payment_ref
number name
reference ref
comment narration
user_id invoice_user_id
amount_ total_company_signed amount_total_signed
residual amount_residual
state state + invoice_payment_state /!\ selection changed
date_invoice invoice_date
date_due invoice_date_due
sent invoice_sent
origin invoice_origin
payment_term_id invoice_payment_term_id
partner_bank_id invoice_partner_bank_id
incoterm_id invoice_incoterm_id
vendor_bill_id invoice_vendor_bill_id
source_email invoice_source_email
vendor_display_name invoice_vendor_display_name
invoice_icon invoice_vendor_icon
cash_rounding_id invoice_cash_rounding_id
sequence_number_next invoice_sequence_number_next
sequence_number_next_prefix invoice_sequence_number_next_prefix
'invoices' subset of account.move can be accessed by using the selection field 'type' or one of the many helpers like is_invoice()
* account.move: now has a valid state 'cancel' that has to be excluded from all business logic
* account.move: field 'amount' renamed into 'amount_total'
* account.move: field 'reverse_entry_id' renamed into 'reversed_entry_id'
* account.move.line: now has a field 'display_type' that has to be excluded from all business logic, in order to support invoice layouting
* account.invoice.line: model removed. Instead, now use account.move.line with following mapping
field (account.invoice.line) field (account.move.line)
---------------------------- -------------------------
invoice_id move_id
uom_id product_uom_id
invoice_line_tax_ids tax_ids
account_analytic_id analytic_account_id
'invoice lines' subset of all account.move.line from a journal entry can be accessed by using the boolean field 'exclude_from_invoice_tab'
* account.invoice.tax: model removed. Instead, now use account.move.line with following mapping
field (account.invoice.tax) field (account.move.line)
--------------------------- -------------------------
invoice_id move_id
account_analytic_id analytic_account_id
amount price_unit
base tax_base_amount
'tax lines' subset of all account.move.line from a journal entry can be accessed by using the relational field 'tax_line_id'
* account.invoice.confirm: model removed. Instead, now use the 'post()' function of account.move
* account.invoice.refund: model removed. Instead, now use account.move.reversal to reverse the entries with the same options as we had for invoices
* account.voucher: model removed. Instead, now use account.move of type in ['out_receipt', 'in_receipt]
* account.voucher.line: model removed. Instead, now use account.move.line
==== Changes made in functions ====
* on account.move, method _run_post_draft_to_post() renamed into _autopost_draft_entries()
* on account.move, method action_account_invoice_payment() renamed into action_invoice_register_payment()
* on account.move, method action_invoice_reconcile_to_check() renamed into action_open_matching_suspense_moves()
* on account.move, method _get_domain_edition_mode_available() renamed into _get_domain_matching_supsense_moves()
* on account.move, method _get_intrastat_country_id() renamed into _get_invoice_intrastat_country_id()
* on account.move.line, method _get_domain_for_edition_mode() renamed into _get_suspense_moves_domain()
* in account.bank.statement, contextual key 'edition_mode' renamed into 'suspense_moves_mode'
Was task 1917430
|
|
The old tree views don't really exist anymore, this odd pseudo-flag to
dispatch between "list" and "tree" tree views has no reason to remain.
Task 1937686
closes odoo/odoo#31243
Signed-off-by: Xavier Morel (xmo) <xmo@odoo.com>
|
|
Purpose of this commit is to give description more "business oriented"
because those descriptions appears in Odoo Studio which is supposed to be used by end users, not only by developers.
Related Task ID : 37311
|
|
Closes #17306
Closes #17303
Closes #17302
Closes #17301
Closes #17300
Closes #17298
Closes #17296
Closes #17295
|
|
* LDAP import: python-ldap is not python3-compatible, pyldap is
Warning: only supported from debian Stretch (current testing)?
https://packages.debian.org/search?searchon=names&keywords=pyldap
* implicitly relative imports
* imports of moved or removed stdlib modules
issue #8530
|
|
reporting menu
|
|
There is a confusion in name of menuitems 'Reports'. For example whe have a lot of printed reports containing reports (eg. Expenses Reports)
For the 'Analysis' reporting views, we should rename this into 'Reporting'.
|
|
Several modules defines records with the external ID `base.foo_bar` while it is
created inside this module (typically menus and groups).
While there is no technical reasons to do so but this may introduce issues:
- these records will not be deleted during uninstall
- if a language is loaded before the installation of the module, it won't be
translated
The uninstallation will only remove the records with an external id linked to
this module (these would only be removed when removing base).
Installing a language before the module will drop the translations not linked
to an existing external id (as it can not be resolved).
This commit correct all the external ids tagged as from base or other incorrect
modules.
|
|
- Split compute function in res.partner into 4 functions as they no more share the same dependencies
- removed dead constraint from 'membership.membership_line' model. That constraint checks if the invoice's date
is greater than membership line's date but the membership line is created before the draft invoice is created
(and that too without date set), hence it can't be raised.(Though, it can be raised if we check it on 'state' field).
|
|
|
|
one child.
Example : Expense/Reports/Expenses --> Expense/Reports
Modified modules : association, fleet, hr_attendance, hr_evaluation, hr_expense, hr_holidays
hr_recruitment, hr_timesheet, im_livechat, mass_mailing, membership, mrp_operations
project, purchase, sale_service
|
|
- Preserved explicit 3rd-party copyright notices
- Explicit boilerplate should not be necessary - copyright law applies
automatically in all countries thanks to Berne Convention + WTO rules,
and a reference to the applicable license is clear enough.
|
|
|
|
|
|
Let 2015 be a year without modelines!
cf #4174
|
|
The graph view has been splitted into pivot/graph view. This commit add
a pivot view whenever a graph view was defined.
|
|
default views, some renaming (py and xml files)
|
|
Branch 8.0 is a **stable** branch. This mean no database schema
changes.
|
|
default views, some renaming (py and xml files)
|
|
* remove old 'day', 'month', 'field' and replace them by the actual
date/datetime field
* remove weird cast to char when creating the view to prevent crash
when grouping on them
* remove duplicates (such as 'creation_date' and 'create_date')
* fix typing errors (field type date defined as a datetime in the
postgres view)
* fix search view definition
|
|
in all searchview, the 'Group By...' looks weird, next to the Custom
Reports and Filters. This change was requested by the upper management
|
|
bzr revid: rma@tinyerp.com-20140414131131-y0qjfqkb2dlrh2o5
|
|
bzr revid: rajmyt@gmail.com-20140304130727-heez8ub1x4jq4dxw
|
|
pivot table (num paid) (addon membership)
bzr revid: ged@openerp.com-20140129144233-4flp69bq188kdy05
|
|
view in pivot mode by default (addon membership)
bzr revid: ged@openerp.com-20131231142807-llb4bvv9njt03ub2
|
|
(and to make sure the result is as close as possible) (addon membership)
bzr revid: ged@openerp.com-20131224102846-ul5tyji72ai5sesb
|
|
bzr revid: vmt@openerp.com-20130415102349-vgcrfok2k5y10cwz
|
|
openerp.addons.decimal_precision
bzr revid: cto@openerp.com-20121217152303-8e3b1x30rlw9cb0d
|
|
bzr revid: vmt@openerp.com-20121206145632-0h1coh5aaem65wsy
|
|
bzr revid: atp@tinyerp.com-20121003052447-99gpby70gy2fbhih
|
|
bzr revid: abo@openerp.com-20121002102915-424prxd74izb1szw
|
|
bzr revid: nco@tinyerp.com-20120927083839-ruhpxzwgdyasodfe
|
|
bzr revid: tch@tinyerp.com-20120808130614-ppieuro8um3fylbt
|
|
bzr revid: tch@tinyerp.com-20120731112804-a0akxtqr1z0uew6w
|
|
bzr revid: tch@tinyerp.com-20120723130624-5mwikpde82bdp9si
|
|
bzr revid: qdp-launchpad@openerp.com-20120622130506-pzz8wqo5p5y902qc
|
|
bzr revid: mdi@tinyerp.com-20120618090824-uc2mggpi6tee059v
|
|
bzr revid: mdi@tinyerp.com-20120528062205-ukjcxs41f917dsk2
|
|
related date field in the search view.
bzr revid: mdi@tinyerp.com-20120522100836-rnmbhv0jx93vev0d
|
|
bzr revid: ssu@tinyerp.com-20120504121326-nqpx2eyqc1qrp04w
|
|
[REF] coding style consistency
lp bug: https://launchpad.net/bugs/525808 fixed
bzr revid: ls@numerigraphe.fr-20120305184003-er00xtj9vtcw7gna
|
|
bzr revid: rco@openerp.com-20111129103537-bi1v2c42ukoa48tw
|
|
bzr revid: fp@tinyerp.com-20111116190124-46utx2qu6lkg8kkr
|
|
bzr revid: kbh@tinyerp.com-20111115092827-8c80hibnp5gnpfw9
|
