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

[14] Quality Control OCA - Exception when creating a related test #823

Closed
oyale opened this issue Jul 8, 2022 · 1 comment
Closed

[14] Quality Control OCA - Exception when creating a related test #823

oyale opened this issue Jul 8, 2022 · 1 comment
Labels
bug stale PR/Issue without recent activity, it'll be soon closed automatically.

Comments

@oyale
Copy link

oyale commented Jul 8, 2022

Module

quality_control_oca

Describe the bug

Can't create a related test. The dropdown with the models and objects is not fullfilled.

To Reproduce

14:

Steps to reproduce the behavior:

  1. Install quality_control_oca
  2. Create a new test and change the type from Generic to Related
  3. Use the dropdown to select a Reference Object
  4. Despite all fields are empty, select, i.e., the second one.
  5. Try to select the second dropdown. An exception is throwed:
Traceback (most recent call last):
  File "/opt/odoo/odoo/http.py", line 640, in _handle_exception
    return super(JsonRequest, self)._handle_exception(exception)
  File "/opt/odoo/odoo/http.py", line 316, in _handle_exception
    raise exception.with_traceback(None) from new_cause
KeyError: '2'

Expected behavior
Either allow to pick a object or not appear at all.

Additional context
Malfunctioning in v12.0 is also reported at #562

There is a commit 494093e deleting the feature from the test part in the 13.0 branch, but the fields in model and view are also present in quality_tool from 12.0 branch.

Should we cherry-pick it to v14 or is it expected that, in addition to inspections, tests can be related?

@oyale oyale added the bug label Jul 8, 2022
@github-actions
Copy link

github-actions bot commented Jan 8, 2023

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

No branches or pull requests

1 participant