Details
-
Bug
-
Resolution: Fixed
-
Low
-
None
Description
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Steps to Reproduce:
- Create a Select List Custom Field;
- Create two additional contexts to the Custom Field;
- Configure the Contexts as described below:
- Default Configuration Scheme for Test Custom Field:
Issue type(s): Global (all issues)
Project(s): Global (all projects)
Options:- Option 1
- Option 2
- Option 3
- Second Configuration Scheme for Test Custom Field:
Issue type(s): Global (all issues)
Project(s): Project A
Options:- Option 2
- Option 3
- Third Configuration Scheme for Test Custom Field:
Issue type(s): Global (all issues)
Project(s): Project B
Options:- Option 1
- Option 3
- Option 4
- Default Configuration Scheme for Test Custom Field:
- Go to the Issue Navigator and add a criteria for this custom field;
- Select all the options (Option 1, Option 2, Option 3, Option 4)
- Save the search as a filter or refresh the page and see the options again.
Expected Results:
After saving the filter/refreshing the page, JIRA would display the options for the Custom Field as it displays before saving the filter:
Actual Results:
JIRA duplicates the selected options and displays a "Value 'yyy' is not valid" icon next to the custom field:
Note: This also happens with other custom field types such as Radio Buttons.
Attachments
Issue Links
- is related to
-
JRASERVER-33092 JIRA Simple Search - Criteria displays 'Value is not Valid'
- Closed