3 answers
1 accepted
Hey Ram, Thanks for the response.
Version is 8.34.0
No major changes in the config settings for it. Simply just the initializer code. There is one field getting changes made in it based on this initial code. (field name is Type.) That code is within the Category field option section and has no impact on the category field itself. Simply reads the category field and sets the appropriate options for Type. (which is basically the same code, just a select list and not a cascading select list.
The same is true for the other projects doing the same thing.
Setup is simple. Setup a JSM project, put a cascading field on the project. Map to that project and form in behaviors. Try to limit your options using the code I provided and change the values to match what you have. Save and take a look. If it works for you, then something else in my environment is off, and I'll have to look from there :D
Thanks
Matt
I am not able to replicate this issue in my environment.
Using the approach that you have mentioned, I am still able to get the Cascade Select List to filter on load time via the Initialiser.
Below is the sample working code that I have used:-
import com.atlassian.jira.component.ComponentAccessor
import com.onresolve.jira.groovy.user.FieldBehaviours
import groovy.transform.BaseScript
@BaseScript FieldBehaviours behaviours
def sampleCascade = getFieldByName('Sample Cascade')
def optionsManager = ComponentAccessor.optionsManager
def filteredCascadeField = customFieldManager.getCustomFieldObject(sampleCascade.fieldId)
def availableConfig = filteredCascadeField.getRelevantConfig(issueContext)
def listCascadeOptions = optionsManager.getOptions(availableConfig)
def availableOptions = [null: 'None']
availableOptions += listCascadeOptions.findAll {it.value in ['Parent1', 'Parent3'] }.collectEntries {[(it.optionId.toString()) : it.value.toString()] }
sampleCascade.setFieldOptions(availableOptions)
Please note that the sample working code above is not 100% exact to your environment. Hence, you must make the required modifications.
Below is a screenshot of the Behaviour configuration:-
If you notice the code I have tested with, it's similar to your approach.
The original parent options for the cascade select list are Parent1, Parent2, and Parent3 as shown in the screenshot below:-
The code I tested excludes Parent2 and only displays Parent1 and Parent3 with the child list options accordingly.
Below is a screenshot of the Cascade Select List from the JSM view. As you can see, only parent options, Parent 1 and Parent 3, are available.
Accordingly, the child options are also available as shown in the screenshots below:-
If your approach matches this but is still not able to work as expected, I suggest trying to temporarily disable all your other Behaviour configurations to ensure that there is no conflict between the configurations.
I hope this helps solve your question. :-)
Thank you and Kind regards,
Ram
Thanks for testing that Ram, I'm not able to reply on that comment for some reason but I'll reply here at least.
So I tried your code out and had the same results.
The only things I changed was the Sample code Field name and the values for a couple options. I'm still seeing all options available under the parent.
I also, commented out the second value (type) in the follow-up section to make sure nothing was overlapping, and the problem still persists. I think the main point of concern for me is that this isn't limited to one project. It Does seem to be limited to Cascading fields though. As the same code works on Single select and multi select lists. This leads me to believe something is going on with cascade options in general. I may raise a ticket with Atlassian, if Appfire themselves can't identify it. (which their latest test suggests they can't, as they repeated your steps pretty much exactly and it worked for them.)
Thanks,
Matt
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.