Recherches récentes
Pas de recherche récente

John Bevan
Adhésion le 29 avr. 2022
·
Dernière activité le 29 avr. 2022
Suivis
0
Abonnés
0
Activité totale
2
Votes
0
Abonnement
1
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 John Bevan
John Bevan a créé une publication,
Feature Request Summary:
Have the auto-suggest feature work when populating Labels for a new Jira ticket.
Description/Use Cases:
Today, if someone makes Labels a Required field it correctly shows up in ZenDesk when creating a Jira ticket from the ZenDesk ticket. However, whilst other lookup fields suggested their available values, Label behaved like a standard text field. Having suggested labels would improve users ability to correctly assign appropriate values to the ticket.
Business impact of limitation or missing feature:
Labels may be entered with typos / inconsistencies.
Users are made to think more than they should be expected to.
Other necessary information or resources:
Looking at Jira's own UI, it seems that the suggested values come from a call to the following API: `https://{tenantname}.atlassian.net/rest/api/1.0/labels/suggest?query=&sessionId={session-id-gui}`. That this includes the Jira session id may be an issue (i.e. as that's user specific), though I believe the Jira integration runs under a dedicated Jira user account; so hopefully the required list can be found by that / the values aren't user-specific?
We've previously logged this with ZenDesk Support: https://support.zendesk.com/hc/requests/10295968
Modification le 29 avr. 2022 · John Bevan
2
Abonnés
5
Votes
1
Commentaire