-
Bug
-
Resolution: Fixed
-
High
-
11
-
Severity 3 - Minor
-
51
-
Hi everyone,
This is Weronika Cabaj from the Jira Cloud Issue Search team. This bug is fixed and I confirmed the functionality to be working as expected. Let us know if you think you are still experiencing this issue.
Sincerely,
Weronika Cabaj
Problem
Attempting to JQL search for cascading select values results in an error like:
An option provided by the function 'cascadeOption' for the field 'testcascadefield' does not exist.
Steps to Reproduce
- Have a cascading select field (i.e. testcascadefield) with at least 2 defined contexts. Let's call them ContextA and ContextBC
- ContextA is configured for ProjectA
- ContextB is configured for 2 projects: ProjectB and ProjectC
- Now configure the value options of ContextA and ContextB to have overlap
- For example, let's say both allows for selecting the value "foobar"
- Ensure that your account does not have "Browse" permissions to ProjectB and ProjectC
- This is the key trigger of the bug
- Now running the JQL:
testcascadefield in cascadeOption("foobar")
- We get the error:
An option provided by the function 'cascadeOption' for the field 'testcascadefield' does not exist.
- Now, if we grant the user account to either "Browse" permissions to either ProjectB or ProjectC, the error does not occur.
So the problem occurs on 2 conditions:
- if there is a context containing no projects that the user account can see
- As long as there's at least 1 project in the context viewable to the user, then the error does not occur.
- if there is a option in the context that is the same value as another context
Expected Behaviour
If an user does not have access to projects defined within a field's context, this should not affect the results for contexts that the user does have proper access to
Actual Behaviour
No issues are returned and the user is instead presented with an error
Workaround
- Avoid using the function. "cascadeOption". So from the above example, use this instead:
testcascadefield in ("foobar")
- Or check each context to ensure that the user has full access to at least one of the contexts listed
- Or avoid having multiple contexts with the same option values
- is cloned from
-
-
- In Progress
-
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Gathering Impact
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-74762] An option provided by the function 'cascadeOption' for the field does not exist
This bug either needs to be fixed or the work arounds need to be applied to the widgets on the dashboard. Specifically the pie chart auto generates the jql using cascadeOption thus when agents in my tenant use their dashboards to drill down to the specific item, they get an error.
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Jira Cloud team
Hi everyone,
This is Weronika Cabaj from the Jira Cloud Issue Search team. This bug is fixed and I confirmed the functionality to be working as expected. Let us know if you think you are still experiencing this issue.
Sincerely,
Weronika Cabaj