Details
-
Bug
-
Resolution: Timed out
-
Medium
-
None
-
5.2.5, 6.0
-
5.02
-
1
-
Severity 2 - Major
-
Description
Steps to reproduce:
- install JIRA
- create custom field type Cascading Select.(eg: "cas")
- set the Issue Type applicable to only one type (not Any Issue Type option). (eg:bug). Refer to screenshot cas.png
- create an issue filter using the Cascading Select. Eg:
resolution=Unresolved AND assignee=admin AND cas="p1" ORDER BY priority DESC - navigate to other place in JIRA
- navigate back to the Issue Navigator and try to access the filter
- JIRA 5.2.x throws Exception in the UI and JIRA 6.x only throws the trace in the logs
2013-10-18 17:55:04,056 http-bio-8680-exec-7 WARN admin 1075x420x1 1kbtv0e 127.0.0.1 /issues/ [customfields.searchers.transformer.AbstractCustomFieldSearchInputTransformer] Searcher customfield_10000 (CascadingSelectCustomFieldSearchInputTransformer) tried to search with context it does not exist for. The search context is com.atlassian.jira.issue.search.SearchContextImpl@4e32d2e1[projectCategoryIds=[],projectIds=[],issueTypeIds=[]] 2013-10-18 17:55:04,059 http-bio-8680-exec-7 ERROR [500ErrorPage.jsp] Exception caught in 500 page Value: 'p1' is an invalid Option com.atlassian.jira.issue.customfields.impl.FieldValidationException: Value: 'p1' is an invalid Option at com.atlassian.jira.issue.customfields.impl.CascadingSelectCFType.getOptionFromStringValue(CascadingSelectCFType.java:481) at com.atlassian.jira.issue.customfields.impl.CascadingSelectCFType.extractOptionFromParams(CascadingSelectCFType.java:464) at com.atlassian.jira.issue.customfields.impl.CascadingSelectCFType.getOptionMapFromCustomFieldParams(CascadingSelectCFType.java:442) at com.atlassian.jira.issue.customfields.impl.CascadingSelectCFType.getValueFromCustomFieldParams(CascadingSelectCFType.java:334) at com.atlassian.jira.issue.customfields.impl.CascadingSelectCFType.getValueFromCustomFieldParams(CascadingSelectCFType.java:69) at com.atlassian.jira.issue.customfields.DefaultCustomFieldValueProvider.getValue(DefaultCustomFieldValueProvider.java:23) at com.atlassian.jira.plugin.customfield.CustomFieldSearcherModuleDescriptorImpl.getViewHtml(CustomFieldSearcherModuleDescriptorImpl.java:110) at com.atlassian.jira.issue.customfields.searchers.renderer.CustomFieldRenderer.getViewHtml(CustomFieldRenderer.java:91) at com.atlassian.jira.issue.customfields.searchers.renderer.CustomFieldRenderer.getViewHtml(CustomFieldRenderer.java:65)
this is tested and reproducible in JIRA 5.2.5 and JIRA 6.0
Expectation
- JIRA to throws a more meaningful message in the JIRA UI
OR - JIRA does not allow issue filter to be save when Custom Field's applicable context is not fullfil
