This fix fixes 2 issues:
- the definition of the row/col structure on the document meta-data
- the content of the headers is within a span so it is editable
Since the the commit that added the barcode listener in the
greeting_message view (aaff7d5d51),
if someone check in and check out and check in again quickly,
during the 5 seconds before the welcome view come back,
multiple rpc where made to call attendance_scan method,
resulting to create inconsistent records in the db.
Typically, a check in records could have been create before
the confirmation of last check out.
Here, we avoid scanning twice the same barcode, between welcome
and greeting message view but also inside the greeting message view
itself.
Employees are now able to check in or check out quickly. Obviously,
if the same employee wants to check in and check out within 5 sec,
he will need to wait the 5 seconds.
Task ID 1878251
Closes PR #27101
Purpose
=======
- Add the SwissQR Code on the invoice in aim to replace the actual ISR
- Improve the settings of the SEPA QR Code to make it more user friendly
Specifications
==============
- ln_ch:
- Add a SwissQR Code on the invoice to fit the Switzerland QR-Bill Format
- Use the "partner_bank_id" field to generate the QR Code
- Add function to get the address number out of the field "street" and "street2"
- account:
- Remove the SEPA QR Code's journal settings from the general setting
- Display the "partner_bank_id" field on the invoice "Other info" page
- Use the "partner_bank_id" field to generate the QR Code
- website_sale:
- Add a check box on the payment acquirers to use the SEPA QR Code on the e-commerce
- Use the payment acquirer "journal_id" field to generate the SEPA QR Code
Two fields number_of_days_display and number_of_hours_display are used to set
a number_of_days field that stores the allocation day count of the allocation.
Those two fields are interface fields. One or another is used depending on the
leave type, depending on how the allocation is done: by hours or by days.
This commit fixes a wrong computation of number of days by correctly setting
a readonly attribute on unused fields as well as removing the inverse on the
interface fields. Using onchange ensure the backend field is correctly
computed. Moreover we could have two times the same tracking message as the
inverse triggers another write and cache could consider the tracking two
times.
Other operators can only cause nonsensical results, while causing
useless slow queries. This is only really meant as a shortcut for
getting messages to moderate.
This commit aims to improve the user experience when using payment acquirers. There currently are no error feedback with some acquirers, which leaves the user wondering what is going on and what is the real status of its payment.
In some cases, the user is currently being redirected to the home page even though the payment has failed. We want to make it more obvious to the user that something unexpected has happened by redirecting to an intermediate page that will provide good feedback on payments status.
Another goal of this commit is to order acquirers by sequence instead of by flow and to select the first acquirer by default. This feature was already implmented in commit fe294fd43e521bd2d339e962f43acf46c3d4cb97, some UI adaptations were needed though.
Related to task #36680Closes#26958
In order to ease the integration with the snailmail posting service provider,
We will generate specific reports with a layout that fits their
criteria.
In short,
* we specify the postition of the recipient's address on the
document
* we force the A4 format
This also support the din5008 type B report.
Reverting some changes introduced in
f29df7fb2e.
By changing the html tag from 'article' to 'page' we were losing the
style on the body of the document. The problem it was supposed to tackle
will be addresed in the future.
Commit: 70e1efd41e
Explicitly added an _order on product.attribute.value.
However the order that should be used first is the one from product.attribute.
It would not make sense to display ipod (white, 8go) and ipod (8go, black).
opw 1883904
Currently, when clicking on 'Create Employee' on the application form,
the employee is correctly created but the form view that is opened
is for a new employee, not the employee that has been created on the fly.
l10n modules are blacklisted on the runbot.
With this commit, a tagged test is added that installs all the l10n
modules. A chart of account is installed in a different company for each
one. This test is a first step to test all l10n. It's intended to be
launched by a runbot cron script.
When getting the context of res_users, all the fields are read but if
the schema is being modified and the modifications are not yet commited
in the database, this leads to a bad query.
With this commit, a read is used to fetch only the needed fields.
Thanks to @RCO for finding this issue that only occurs in specific
planetary alignment.
Before that, the administrator could use accounting features by default. This is not what we want, the group only gets assigned by default when installing account_accountant, on enterprise.
Impacted applications: hr, maintenance, mass mailing, survey, base
(attachment), product, stock (and dependencies), project (and dependencies),
event (and dependencies).
This commit is related to task #1875881 and closes PR #26938 .
Specifications: improve menu organization, search filters and groupby, reorder
filters, update some field labels.
Add search view for event type and make tree views for locations, sponsor
types and track tags editable bottom.
This commit is related to task #1878516 and PR #2649 .
Specifications: improve menu organization, search filters and groupby, reorder
filters, update some field labels.
This commit is related to task #1875881 and PR #26938 .
Specifications: improve menu and action names, search filters and groupby,
reorder filters, update some field labels.
This commit is related to task #1875881 and PR #26938 .
The `timesheet_uom` is a fake widget: it is bind in field widget
registry on other existing widget depending on the session_info
preferences (e.i.: float_time, float_toggle, ...). Therefore, it
does not have formatter/parser methods in the field utils method.
This commit binds the formatter and the parser of the widget on which
`timesheet_uom` is bind, to make it coherent. This avoid having a
traceback on pivot view when the `timesheet_uom` widget is set on
a field node.
Since saas-11.4 the subtype dropdown don't keep changes of subtype.
Before saas-11.4 the update was relying on the fact that the follower id
changes on each subtype edition. This is no longer the case.
The test is addapted to remove the hack simulating this behaviour.
The read_followers route is not called if no there is no changes
in the follower ids
https://github.com/odoo/odoo/blob/905e01921f3c3ef43ace6fc537d1d8c0d280002c/addons/mail/static/src/js/followers.js#L195
Leading to the follower list not being update
Note that the subtype update in dropdown was working fine after adding a
new follower: the read_followers will return a None as suptype when called
for a list of partner not containing the current user. Since the subtypes
was falsy, the render was not rendering the dropdown again, keeping
the value of the checkboxes. We can still create some inconsistency by
editing the subtype from the follower list. To avoid that a check is made
when updating subtypes after calling read_followers.
The chosen solution here is to keep the update on subtypes in memory.
This will avoid a call on read_followers to fetch information that we
already know, using the assumption that the operation was successfull
whish should be the case when a user edit subtypes on a record
he has access to.
Others solutions:
-force the call to read_followers with the current user, maybe by removing
it from this.follower after editing subtypes.
-call read_subscription_data explicitely
Obviously follower.js should be refactored to fix this a better way.
Task: #1886982
PR: #27093
* web_editor, website_slides
Current system is styling all navbars with the user color. This was not
the expected behavior but it is in fact quite nice, so we decided to
keep it. There was however a problem: choosing the menu text color only
applied to the main navbar (as it was an xpath toggling the navbar-dark
class).
This commit solves the problem by forcing navbar-light to behave as
navbar-dark automatically if the menu background is dark, and this
without any JS or extra CSS rules. This allows to get rid of the menu
text color option.
This commit also reviews the light and dark colors which are used when
website is not installed.
Impacted applications: crm (and dependencies), sale (and website_sale), point
of sale, accounting, purchase, base/mail, calendar, mrp.
This commit is related to task #1878516 and closes PR #26929 .
Specifications: improve menu organization, search filters and groupby, reorder
filters, update some field labels.
This commit is related to task #1878516 and PR #26929 .
Specifications: improve menu organization, search filters and groupby, reorder
filters, update some field labels.
This commit is related to task #1878516 and PR #26929 .
As all information present in this report can be found in the opportunities
dashboard this report can be removed.
This commit is related to task #1878516 and PR #26929 .
Specifications: improve menu organization, search filters and groupby, reorder
filters, update some field labels.
crm
===
Restructure the menus as
* Sales
* My Pipeline (default filter: My Opportunities)
* My Quotations (default filter: My Quotations)
* Team Pipelines (opens sales teams in kanban view)
* Customers
* Leads
* Leads
* Scoring Rules
* Teams Assignation
* Leads Assignation
sale_crm
=========
Change the parent menu for 'My Quotation' menu item as menus are changed in
sales: crm.crm_menu_pipeline -> crm.crm_menu_sales
website_crm_partner_assign
==========================
Removed the menu and its action: crm -> Reporting -> Opp. Assignment
Change the menu sequence for crm -> Reporting -> Partnerships. Menu should
display as
* Leads
* Pipeline
* Activities
* Scoring Page views
* Partnerships
This commit is related to task #1878516 and PR #26929 .
This css rule is used notably by bs4 .card-deck. The fix is needed to make sure multiple cards inside a card-deck prints on a new line instead of overflowing horizontally out of the view.
PR: #26801
task-1876864
Adapt the left menu to correctly display each heading on a new line.
Always show the left menu navigation, especially on mobile where it is the most useful to quickly go below.
Remove unnecessary code from the quotation builder template.
PR: #26801
task-1876864
The menu wasn't correctly responsive. Now we always set the left and bottom border on the list elements, and remove them from the parent. This way the style will be correct even if the elements flex to the same line on some screen size.
PR: #26801
task-1876864
Vincent Schippefilt