최근 검색

최근 검색 없음

Explore 사용법: 티켓 및 문서에 대한 클릭 가능한 링크 구성

image avatar

Erin O'Callaghan

Zendesk Documentation Team

2025년 3월 05일에 편집됨

12

0

댓글 16개

날짜
    최신순
      image avatar

      Dainne Kiara Lucena-Laxamana

      Hi 6110941897754 ,

      You can configure any ID attribute into clickable links as long as there is an ID attribute for the object.

      0

      image avatar

      Efrat Barak Zadok

      Can I configure clickable links to related Jira tickets?

      0

      image avatar

      Erin O'Callaghan

      We've updated this article to note that clickable links are now available by default for many Zendesk attributes. As a result, we've also updated the example in this article to focus on Zendesk Guide article IDs, which aren't clickable by default but can be made clickable using this recipe.

      0

      image avatar

      Permanently deleted user

      @Cheeny Aban - Thank you!

      0

      image avatar

      Cheeny Aban

      Hi CaSonya,

      As of the moment, this functionality is limited to what is included in this Article. We understand your need for this added functionality so I marking your comment as Product Feedback. We also suggest that you post on our Product Feedback Forum. Threads with a high level of engagement ultimately get flagged for product managers to review when they go through roadmap planning.

       

      -1

      image avatar

      Jon Durlauf

      Any update on the ETA for clickable links for ID attributes in drillthrough?

      1

      image avatar

      Permanently deleted user

      Hi, I created a query for unsolved tickets by client.  Is there anyway to add the clickable link to the results?  I want to be able to click on the total of unsolved tickets and see the ticket#'s associated with a link to each ticket.

       

       

      0

      image avatar

      Sabra

      Hey Bharathi Kakilate! You can use the following formula in a Standard Calculated Attribute in order to create Jira hyperlinks. You'll need to replace YOURJIRASUBDOMAIN with the name of your subdomain for your Jira instance. You'll also want to make sure that the field used in the formula corresponds to the ticket field that is storing your Jira Ticket ID, which in the example is [Jira::Key].

      LINK("https://YOURJIRASUBDOMAIN.atlassian.net/browse/"+[Jira::Key],[Jira::Key])

      Once you have this attribute added to your Rows panel, you'll want to double check that you've set the Text interpretation to HTML from the Chart configuration > Chart menu.

      1

      image avatar

      Bharathi Kakilate

      I tried to use a similar concept of using attributes to add hyperlinks to our Jira issues and couldn't create attributes. Anyone else with this issue or found way to work with adding jira hyperlinks on explore dashboards?

      (We are using Single line text to sync the Jira Ticket ID from Jira to Zendesk)

      0

      image avatar

      Henkka (Pepron)

      Hi Bart,

      If I understood correctly this tip earlier in the thread might do the trick:

      Unrelated tip: You can easily also create user and organization links with the following calculated attributes:

      LINK("https://YOURORGANIZATION.zendesk.com/agent/users/"+[Requester ID],[Requester name])

      And

      LINK("https://YOURORGANIZATION.zendesk.com/agent/organizations/"+[Requester Organization ID],[Requester organization Name])

      OR

      LINK("https://YOURORGANIZATION.zendesk.com/agent/users/"+[Ticket requester ID],[Ticket requester name])

      And

      LINK("https://YOURORGANIZATION.zendesk.com/agent/organizations/"+[Ticket organization ID],[Ticket organization name])

       

      For your use case if I understood it correctly _ticket_ requester would be good but if you're using these for user/organization spesific queries then you could use also use Requester ID/Organization ID without _ticket_.

      In the latter just keep in mind that if you've activated multiple organizations this will show you always Requesters/Users default organization while if you're doing ticket spesific queries Ticket Requester/Organization ID will always bring up the right organization based on the ticket.

      Unfortunately none of these work with drillins etc for now so you probably need to do a Table query like in the example in this article

      0

      로그인하세요.

      계정 세부 정보

      세부 정보를 보려면 로그인하세요.

      로그인하여 계정 세부 정보를 한 눈에 확인하세요.

      로그인

      추가 콘텐츠