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

Version and Build Is Not Loaded When Searching Bugs #2704

Closed
dnomyar90 opened this issue Feb 2, 2022 · 0 comments
Closed

Version and Build Is Not Loaded When Searching Bugs #2704

dnomyar90 opened this issue Feb 2, 2022 · 0 comments
Labels

Comments

@dnomyar90
Copy link

HINT: try to reproduce bugs and errors at https://public.tenant.kiwitcms.org!
This is always running the latest version and will automatically submit
traceback and debugging information to us!

Description of problem

List of a product's version and build is not loaded when searching for bugs

Version or commit hash (if applicable)

Tested on 10.4 (Local hosting) and 11.0 Enterprise (Public tenant Kiwi)

Steps to Reproduce

  1. Go to https://public.tenant.kiwitcms.org/bugs/search/
  2. Filter product "Kiwi TCMS"
  3. Try to filter based on Version and/or Build

Actual results

No list of Version and Build is loaded on the dropdown list

Expected results

List of Version and Build is loaded on dropdown as per the product selected

Additional info (Python traceback, logs, etc.)

Screen Shot 2022-02-02 at 10 14 52

Screen Shot 2022-02-02 at 10 14 46

@atodorov atodorov added the bug label Feb 2, 2022
atodorov added a commit that referenced this issue Feb 2, 2022
On pages where a single selection can be made tha value is a string,
while on pages with multiple selection the value is an array. This
causes the API to not return any values b/c the selector

	product__in="string"

doesn't work on Postgres.

Making sure that we always pass array as an argument to the ORM selector
works on all database backends.
atodorov added a commit that referenced this issue Feb 2, 2022
On pages where a single selection can be made tha value is a string,
while on pages with multiple selection the value is an array. This
causes the API to not return any values b/c the selector

	product__in="string"

doesn't work on Postgres.

Making sure that we always pass array as an argument to the ORM selector
works on all database backends.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

No branches or pull requests

2 participants