Recherches récentes
Pas de recherche récente

Ben Lakos
Adhésion le 22 oct. 2021
·
Dernière activité le 28 févr. 2024
Suivis
0
Abonnés
0
Activité totale
13
Votes
10
Abonnements
2
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Ben Lakos
Ben Lakos a ajouté un commentaire,
Hi Ashwin Raju
Has there been any progress on dynamic filtering for relationship fields?
I remember being so excited when relationship fields became possible, and then so disappointed when I realised how limited their use in Views and Triggers were (at least in our use cases).
To me, at a pretty fundamental level, if I can eg use the 'Assignee' field in defining Views and Triggers, then I'd expect the same functionality for any other relationship field that also utilises Users. To have only a subset of that functionality makes the whole feature far less useable.
Our specific use case is pretty simple and I would have thought applicable to many others:
- we have two agents working on each ticket
- the second person obviously wants to keep across tickets that they are responsible for
- we therefore want the 'Your Tickets' view to include tickets that have either 'Assignee' OR 'Custom Field' set to (current user)
- similarly, we want the 'You've been assigned a ticket' notification to go to users that have been selected in the 'Assignee' field OR the 'Custom field'
The fact that we can't do this makes the feature very limited in usability for us.
Afficher le commentaire · Publication le 28 févr. 2024 · Ben Lakos
0
Abonnés
0
Votes
0
Commentaire