The "Page Tips" entry paragraph on the "Field Dependencies" setup page says that :
- Field dependencies are filters that allow you to change the contents of a picklist based on the value of another field. You can create dependencies between two pick lists or between a pick list and a multi-picklist.
This was the way when we started using Desk about 3,5 years ago and we did ask you about its design also back then.
Right now we are doing a house-cleaning for data analysis purposes where we are trying to enhance and fine-tune our ticket classification structure. We still do need to be able to use a 3-tier problem and solution classification structure where a ticket can be classified with more than one problem and solution class. This means that the first 2 tiers do also have to be defined as multi-select picklist fields as the 3. and last tier.
Back in the day, you did not clearly state if there was a design issue with defining the "Parent Field" as a multi-select picklist field or if this was something possible but that you didn't plan for.
I'm asking you one more time; Is this possible and if yes when would we be able to have this feature?
Do we have to provide our agents with large tables printed onto huge cardboards for them to look up for the correct field dependency matches to be able to use multiple problem-solution tags in single tickets? Even this absurd cardboard solution would allow for errors because using no field dependencies means manually selecting the classification level field values which can cause human errors.