If it's easier to implement, one could define both parameters as mutually exclusive, i.e. you can use only one of them. I don't really care about the openTo parameter, because I don't have a scenario where it may be useful to me.
Marius Dumitru Florea on 11/Mar/25 09:56
Simon Urli the way I see it, the two parameters, openTo and openToLevel are independent, and don't affect each other:
openToLevel is taken into account server-side when fetching the tree data to:
include in the JSON the descendants up the specified level
mark in the JSON the parent nodes from those levels as "expanded"
openTo is taken into account client-side, after the tree data is loaded and the tree is displayed, and its behavior doesn't change:
if the target tree node is already loaded then expand all its parent nodes (if not already expanded) and select the target node
otherwise, fetch from the server the path of the target node and then load and expand all its ancestor nodes (of course, if they are not already loaded and expanded)
So adding the new parameter shouldn't have any effect on the openTo parameter. It should not matter for the openTo if the tree is already loaded and expanded up to N level.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.