zammad
zammad copied to clipboard
zammad
Enhance> object manager> (multi) tree select: add possibility to disable options
Used Zammad Version
6.2.0-alpha-1697722482.057e90b3.bookworm
Environment
- Installation method: any
- Operating system (if you're unsure:
cat /etc/os-release): any - Database + version: any
- Elasticsearch version: any
- Browser + version: any
Actual behaviour
When I want to force users to select the endpoints/leaves of (multi) tree selects I need to create a Core Workflow to disable all nodes with sub-nodes. Which means, when I make changes to the structure of the attribute, I need to remember, that I also update the Core Workflow.
Expected behaviour
I want to achieve this goal in the object manager alone. Bei either having the choice to disable specific nodes, or by having a generic setting to disallow node selection for nodes with sub-nodes.
Steps to reproduce the behaviour
Try to build a tree select where users are forced to select a leaf of the tree.
Support Ticket
No response
I'm sure this is a bug and no feature request or a general question.
no
I've exactly the same request. In fact it was the behaviour until 6.1. 6.2 fixed some oddities with tree select (https://github.com/zammad/zammad/issues/4830) but introduced this side effect that non-leaf nodes are now selectable without any easy way to disable them.
For example we added to the ticket form an object team whose value is a tree representing the structure of the organization but we want the user to be able to select only a leaf in the structure tree.
It is possible, but cumbersome. You can disable the "nodes" via Core Workflow with "remove option". But you would manually need to add all nodes that have leaves to that Core Workflow, and you would need to update the Core Worklow, when you make changes to the attribute.
@YetAnotherGerrit thus the ticket! It is ecactly what we don't want to do. Team strucure is evolving regularly and we want the update procees to remain simple. Zammad should provide an option for tree select when added to a core workflow, like "show only leaves" in addition to "show".
Have the same exact issue... We control all our help topics using the select tree view, makes it really easy to manage.
But unfortunately we find quite often users are just selecting the branches rather than picking a leaf. I have so far tried to stay away from creating a tedious workflow for this and it would be so good to have a built in option for this.
As mentioned in the customer meeting (regarding T#10151949), a top-level field to be removed via the core workflow ("remove" action) is still visible if it has subcategories, only it is shown crossed out.
@Suhopoljac this issue is not about that. It's about the possibility to disable options in a tree select via object manager, rather than Core Workflows.
In my humble opinion, although this can be achieved using work flows, this is not a very user friendly way of doing itv.
Once the parent is disabled, user is expected to know to use the ">" to navigate to the children/leaf in the tree. The area covered by the arrow is much smaller in comparison to the text field so it is not very intuitive. Also the disabled arrow pointer gives the impression the option is not available.
It would be nice to have an option which disables selection of the parents and preferably assign the function of the ">" key to the parent. I.e. When this option is selected, then clicks on the parent items on the object should just reveal the child items.
I am not sure about the complexity of implementing this but it would be a really useful addition and would make managing of help topics a lot easier.
@ozturkinc I see your point. But your suggestion is about the design of the tree select, this issue is about an option in the admin interface.
Please use the community forum for Feature Requests and discussions about them: https://community.zammad.org/c/stuff-you-like-zammad-to-have-feel-free-to-discuss-and-add-proposals/6/none
@YetAnotherGerrit the big question here is how to solve it. I guess you would need operators for add option recursive, remove option recursive and set fixed to recursive. Else you might destroy the setup of existing systems. Or we change it for the existing ones in a minor/major release and force users by release notes to manual changes.
@rolfschmidt what you are talking is again a different issue: https://github.com/zammad/zammad/issues/5019
