-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
6.4.12, 6.4.13, 7.1.2, 7.2.1, 7.2.2, 7.2.3, 8.20.10, 9.4.16, 9.4.21
-
6.04
-
38
-
Severity 3 - Minor
-
24
-
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 access to at least one of the projects listed
- Note, you can create a blank project without any issues, assign it to a restricted context of your cascading field, give all users "browse project" permissions, and cascadeOption JQL condition will work as intended after that, since all users will have access to at least 1 project in the restrictive context.
- Or avoid having multiple contexts with the same option values
- has a derivative of
-
-
- Gathering Impact
-
- is related to
-
-
- Closed
-
- was cloned as
-
-
- Closed
-
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
[JRASERVER-62591] An option provided by the function 'cascadeOption' for the field does not exist
Hi,
we also "suffer" this problem. We have noticed that it does not happened if the user is in the "jira-system-administrator" user group
Dear Atlassian Team,
Our Company also using cascaded fields with different contexts and overlap in their options. We are also waiting to have a fix of this error.
Good afternoon
We are still having issues with this and are using Jira software version 8.13.6. Please let us know if it has been fixed or if there are any reliable workarounds for this
Good morning,
The problem persist in the Server's version 8.13.24
It would be recommended that the issue was taked care or closed like in the related issue in Cloud JRACLOUD-74762, please.
Regards.
Same problem here, after granting user access to another project it start work, but of course we dont want him to have access to that project.
A user is unable to use his cascade select field in gadgets because of this bug that doesn't have a realistic workaround.
This may have been what Petr Novy mentioned in his comment, but we get this to work by using the custom field ID rather than the custom field name. So, our JQL looks like this: cf[21801] in cascadeOption ("Option 1") for a search of just the first level. Obviously, you need to know the custom field ID to get it to work.
Hi,
We are facing this problem since several months. Please provide a solution.
Thanks