Infos:
- Used Zammad version: 5.3.1
- Used Zammad installation type: package
- Operating system: CentOS Stream 8
- Browser + version: Chrome 104 / Opera 94
Expected behavior:
-
I added a Category attribute to my ticket object defined as a tree_select. Categories (top level parents in the tree_select) have subcategories. 3 categories are defined as follow :
- A : subcategories (children) AB, AC
- B : subcategories BA, BB, BC
- C : no subcategories
-
I have a workflow displaying a subset of Category attribute values (Category
fixed
to a few parents) when a specific group is selected. Let sayA
andC
for example. -
I expect to be able to select either
A
orAB
orAC
orC
Actual behavior:
-
The Category list in the ticket creation shows
A
andC
, with a>
on the right side ofA
suggesting that I’ll be able to select subcategories but if I click on it, I seeA
again instead ofAB
orAC
. -
To fix the problem with the fixed list of values for Category, I have to add children instead of parent Category values in the Core Workflow but it is a lot of work and difficult to maintain if you have many subvalues to add and changing them from time to time.
-
This behaviour is inconsistent with the fact that if the Cateogory attribute is added in the Core Workflow without restricting the possible values (
displayed
), you have access to all the subcategories.
Steps to reproduce the behavior:
- See above