Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kanban mobile add new column #31235

Closed

Conversation

msh-odoo
Copy link
Contributor

Use a command to add the created record, otherwise it simply does not work.

closes odoo#30148
@C3POdoo C3POdoo added the RD research & development, internal work label Feb 19, 2019
kig-odoo and others added 5 commits February 20, 2019 06:32
- add missing docstrings
- correctly order functions
- move functions in correct sections
- follow JS guidelines

closes odoo#31261
Before this commit: select more than two groupbys
in a graph view would have no impact at all if mode
'bar' or 'line' is selected.

This commit allows to correctly handle more than
two groupbys in all modes.

Task ID: 1917948

closes odoo#29673
Payment providers can be used without eCommerce. Therefore, we should be
able to access the payment transactions with only `sale` installed.

opw-1941591

closes odoo#31270
Remove the corporate CLA (only cantecim has contributed in the past) and signs
an individual CLA file instead

closes odoo#31177
@robodoo robodoo added the CI 🤖 Robodoo has seen passing statuses label Feb 21, 2019
svs-odoo and others added 7 commits February 13, 2019 15:40
Before this commit, when UoM was displayed, it wasn't specify if cost
referred to 'Unit of Measure' or 'Purchase Unit of Measure'.
To avoid ambiguity, it's now specified.

This apply when 'Units of Measure' is ticked in settings.

Task #1937177

closes odoo#31070
In small devices, onboarding bars are displayed vertial, which
takes too much screen space, and user has to scroll down
a lot to view actual content.

This commit improves the behavior by showing onboarding bars
horizontally (with scrolling) in small devices also, and thus
occupying minimal screen space.

task: 1929048

closes odoo#30823
Let the database be in multi-company with unshared contact catalog.
Let F be a filter "('partner_id', 'not ilike', 'string')" on invoices.
If there is a contact which parent belongs to another company,
then this parent cannot be read.
Thus the name_get on partner can create an access error.
As a result applying the filter F would fail and return no results.

It generally doesn't make much sense to have a contact company X, which belongs
to the Odoo Company OC1, while its child contacts are in another Odoo company,
since many fields are directly computed from the parent.
However it is useful to have X belongs to no company, while it has child
contacts X>Yi belonging to company OCi.
In the first case it can create access errors interrupting the normal flow of
operations, while the latter should not.

To forbid the first case while allowing the second, we synchronize company_id,
but add a special case to ignore it if it set to False.

Note that PR#30997 should be used in case the name_get causes an error for
another reason that is deemed a legitimate use-case.

opw 1933862

closes odoo#31364
When users create an automated action to trigger when a record is updated,
they assume each update is 'atomic' in some sense.
It is not the case, as one write may trigger many write, some in recompute.
As a result, any update may trigger a dozen actions (or more).
We add a field wich allows us to specify which field we want to watch.
For instance, you could select the field 'state on quotation',
and thus only action would be triggered on confirming the quotation.

The link_field_id is a field that allows to link a record of the source model
to a new record of the target model, through a many2one.
However many target records can be created, so every one of them
(except the last) ends up orphan.
We allow for one2many and many2many fields to be used,
and in these cases we add the newly created record to the list.

opw 1910671
PutAwayStrategy model was deleted and FixedPutAwayStrategy model was
renamed into PutAwayRule.
Now, each location can contain multiple putaway rules, each rule
applying either on product or on product category.

The purpose is to:
-   Add more visibility on putaway settings (with a stat
    button on product, product category and location views, and a
    submenu item in Product configuration menu).

-   Change putaway model to avoid redundancy.

Task #1935169

closes odoo#30889
 - while clicking on send now button in mass mailing app it throws error due to wysiwyg undefined.

closes odoo#30533
This commit ameliorates the tooltips and the legend
of the graph view in its different modes (bar, line, and pie).

Related task id: 1917940

Co-authored-by: Mohammed Shekha <msh@openerp.com>
Co-authored-by: Mathieu Duckerts-Antoine <dam@odoo.com>

closes odoo#29747
@msh-odoo msh-odoo force-pushed the master-kanban-mobile-add-column-msh branch from cba1eba to 24a30af Compare February 25, 2019 13:19
@robodoo robodoo added CI 🤖 Robodoo has seen passing statuses and removed CI 🤖 Robodoo has seen passing statuses labels Feb 25, 2019
@msh-odoo msh-odoo force-pushed the master-kanban-mobile-add-column-msh branch from f5ce2e9 to a694b91 Compare February 26, 2019 05:24
@robodoo robodoo added the CI 🤖 Robodoo has seen passing statuses label Feb 26, 2019
nim-odoo and others added 8 commits February 26, 2019 08:22
User might be confused by the help: they think the vendor cannot sell
the product below this quantity, which is not what the field depicts.

Improve the label and the help of the `min_qty` field to avoid
confusion.

opw-1943511

closes odoo#31414
* web_editor, website, survey, im_livechat

Part of odoo#29442
task-1932066
In preparation to future commits, the WebsiteRoot instantiation is moved
in an other file than its definition.

Part of odoo#29442
task-1932066
* im_livechat, survey, website_forum

When website is installed, the JavaScript code has access to utilities
to define improved widgets which are automatically attached to existing
DOM elements on page load. Those mechanics are more and more needed in
portal which does not depend on website (as it is website which depends
on portal). This commit moves part of website JS to web, so that it can
be used by all 'frontend' apps whose only common dependency is web
(portal, survey, auth_signup, ...).

This PR also questioned several other similar issues which will be
handled later like:

- website should maybe not depends on portal but only on http_routing

- part of portal should be moved to http_routing and http_routing
  should be renamed (especially for frontend layouts, etc) so that apps
  like survey can reuse some common code

Part of odoo#29442
task-1932066
Not sure this one is still useful but best to integrate it as a
public widget.

Part of odoo#29442
task-1932066
* account, auth_signup, payment, portal, project, sale, sale_management,
  web_unsplash, website, website_mail, website_rating, website_sale

This commit does probably not do what is stated for all non-website apps
but it is a first step. It also uses the system in apps which could have
already used it but did not.

Part of odoo#29442
task-1932066
qsm-odoo and others added 15 commits February 27, 2019 10:28
Bootstrap 4.3.1 introduced tooltip sanitization. Odoo should normally
use tooltips for secure content anyway, so this commit disables this
sanitization. A proper analyse of our tooltip should however be done
to know if sanitizing is needed (it can also be enabled case by case).
* web, im_livechat, survey, web_editor, website_forum, account,
  auth_signup, payment, portal, project, sale, sale_management,
  web_unsplash, website_mail, website_rating, website_sale,
  website_blog, website_crm_partner_assign, website_event_track,
  website_links, website_slides, website_mail_channel,
  website_mass_mailing, website_sale_comparison, website_sale_delivery,
  website_sale_wishlist, website_event, website_form,
  website_sale_stock, website_twitter

When website is installed, the JavaScript code has access to utilities
to define improved widgets which are automatically attached to existing
DOM elements on page load. Those mechanics are more and more needed in
portal which does not depend on website (as it is website which depends
on portal). This moves part of website JS to web, so that it can be used by all
'frontend' apps whose only common dependency is web (portal, survey, ...).

See sub-commits for details.

task-1932066

closes odoo#29442
See https://blog.getbootstrap.com/2019/02/11/bootstrap-4-3-0/
and https://blog.getbootstrap.com/2019/02/13/bootstrap-4-3-1-and-3-4-1/

Again, some fixes were added in this version and not in a 4.2.x version
so there is no clean way to backport them in 12.0 / saas-12.2.
If needed, the file bootstrap_review.scss is there for that.

Among the new features, two notable ones:
- The '.modal-dialog-scrollable' class which does what odoo already
  implemented for all its modals. So we could remove our custom code in
  a next update.
- Responsive font sizes ! Plan was to develop something similar for the
  website, so this comes at the right time. The behavior is opt-in, we
  will enable it in a next update.

task-1944790

closes odoo#31401
'transaction_ids' is a field defined in 'account_payment' but used in 'account'.
Then, the portal generates a traceback with only 'account' installed.
-incoterm_id in account/models/account_invoice.py
-incoterms_id in sale_stock/models/account_invoice.py

closes odoo#31463
Oversight of previous foward-port.
@robodoo robodoo added CI 🤖 Robodoo has seen passing statuses and removed CI 🤖 Robodoo has seen passing statuses labels Mar 1, 2019
svs-odoo and others added 3 commits March 1, 2019 10:12
When a scrap move is created, not with the scrap button but with a
scraped operation, the move stay visible in movelines, by opposition of
scrap moves created with the scrap button.

Also, when you create a scrap from a delivery order, it'll try to
prefill the location field with the location where the reserved product
is stored.

Task #1940511

closes odoo#31500
Was called "group user" while was applying to manager

Fixes odoo#31300

closes odoo#31537
Create one extra tab for Quick Create columns, when user click on that tab show quick create column widget(always unfolded),
once column added move back to quick create column widget again so that new column can be added again,
if window clicked, that is clicked outside the quick create widget move to previous column,
if quick create widget is open and Create button of control panel is clicked then move to first column and then open quick create record there,
if quick create column's add button is clicked without entering text in input element then discard quick create and move to previous column.

Related to task: #1893137

Co-authored-by: Ankit Sathvara <asa@odoo.com>
@msh-odoo msh-odoo force-pushed the master-kanban-mobile-add-column-msh branch from 2c2942b to 8064fc4 Compare March 4, 2019 09:03
@robodoo robodoo removed the CI 🤖 Robodoo has seen passing statuses label Mar 4, 2019
@msh-odoo
Copy link
Contributor Author

msh-odoo commented Mar 4, 2019

LGTM

@robodoo robodoo added the CI 🤖 Robodoo has seen passing statuses label Mar 4, 2019
@pparidans
Copy link
Contributor

Closed by #40722

@pparidans pparidans closed this Nov 25, 2019
@robodoo robodoo added closed 💔 and removed CI 🤖 Robodoo has seen passing statuses labels Nov 25, 2019
@adr-odoo adr-odoo deleted the master-kanban-mobile-add-column-msh branch December 4, 2019 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RD research & development, internal work
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet