Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

All work

Select view

Select search mode

 
50 of 85

Switching array operators disables the "Test" button

Done

Description

Steps to reproduce:

  1. Open the query builder in one of the apps that uses it, for an entity type with an array-type field that provides available values (e.g., Statistical code names in Instances)

  2. Select the array field

  3. Set the operator to “contains all”

  4. Select at least one value

  5. Change the operator to “contains any”

Actual behavior: The selected values remain after switching operators, but the “Test” button is disabled

Expected behavior: Since the visible query condition is still valid, the “Test” button should still be enabled

 

Note: You can work around the bug by changing the condition values in any way (e.g., add a value, then remove it)

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

2

Checklist

hide

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Firebird

Fix versions

Release

Ramsons (R2 2024)

RCA Group

Implementation coding issue

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created July 23, 2024 at 5:33 PM
Updated August 19, 2024 at 8:30 PM
Resolved August 14, 2024 at 11:10 AM

Activity

Show:

Kathleen MooreAugust 14, 2024 at 11:10 AM

Confirmed this is now working as expected.

Emma_HaroyanAugust 14, 2024 at 10:19 AM

could you confirm and close the ticket, please?

Emma_HaroyanAugust 14, 2024 at 10:18 AM

Tested on Snapshot.

The bugs is fixed.

Matt WeaverAugust 12, 2024 at 5:46 PM

, that works and is probably better than what I put for the expected behavior, since it’s consistent with the other query operators

Vadym ShchekotilinAugust 12, 2024 at 12:19 PM

Hi , In the current implementation of query-plugin, when changing an operator, the value for "value control" (which is very right) is always reset. The current bug is due to the fact that for certain reasons, the multi selection value was reset but this was not displayed on the UI and we still saw the values ​​in the control. I fixed this part, you can see the current behavior after the fix on GIF.

This is a little different from your “Expected result”, but if we need this behavior, I would suggest placing this requirement in a separate story, since for consistency this must be done for all operators and all value selectors but not only for contains-related.

TestRail: Cases
TestRail: Runs