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

Filters addon block doesn't work in some cases #4589

Open
kirill-tolochko opened this issue Jan 29, 2025 · 0 comments
Open

Filters addon block doesn't work in some cases #4589

kirill-tolochko opened this issue Jan 29, 2025 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@kirill-tolochko
Copy link
Collaborator

Problem description

If user tries to set up filters addon block with Query type: User-defined, he isn't able to get any data with this filter - 422 error

Step to reproduce

Steps to reproduce the behavior:

  1. Import iRec4 policy
  2. Find issue_by_device block, change Query type from Equal to User-defined
  3. Put the policy in the dry run mode, run flow - create and approve application, create and approve few devices, and check Issue Request page under the User (not SR/Administrator)

Expected behavior

User is able to change filter's type: set Equal, Not equal, Greater than etc.

Actual behavior

There is 422 error, filter isn't working
2025-01-29T10:30:46.169Z [GUARDIAN_SERVICE]: Error: Unknown filter type: undefined
at file:/guardian/guardian-service/dist/helpers/guardians.js:95:32
at SubscriptionImpl.callback (file:/guardian/common/dist/mq/nats-service.js:49:29)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants