pablo.torres

Hi Victor, hope you're doing well too.

I mean the thing is: there's actually no report on “who is the parent” of the child ticket.

You can get information of the child tickets through the filter “channel:side_conversation” but nothing about the origin ticket.

I know for a fact that you can get that information through API though, in an order similar as this:

• Get the info of the child ticket with its id (knowing that it's already a child, through Explore and the aforementioned channel filter), see the next example.

• Obtain the last part of the “external_id”, after :ticket:, because there it shows the id of the father ticket.
• Search the parent ticket through that id.

Only after that you can get information (only through API) of the parent you can try to understand the status of the parent ticket.

Me question was “is there anything that Zendesk can offer to us through Explore?” 

Hi team, I wanted to let this here in case anyone has any workaround about the following problem:

• My team can't send information from Jira to Zendesk.

There's a need in sending information regarding solved issues from Jira to Zendesk but they don't get into Zendesk.

Could you please give some advices or different ways of getting around this problem, please?

Hi Team.

Working with macros I've come to realize that when you use macros with hyperlinks, they get separated from the text and they end up showing like a text/link.

Can the Support Team consider this as a needed feature not only for Chat, but for Messaging as well.

I need to send an specific URL that is really long but I don't want to show it to the client, but with the macro they end up getting the whole long tring of link.

Please take it as something to work on.

Hi Team.

I wanted to put in the table the following feature that needs to be added to the current Chat:

• End Chat (Chat Legacy).

So far I've worked with a client that can't migrate to Messaging and the new Chat only because of that feature and it's a must for their core business.

Hi Community!

Along with my greetings I wanted to put in the table the following requirement:

• Having information in Explore that can help us (agents/admins) do a follow-up to the Side Conversations tickets with their ticket status, having the information of which ticket they originated from.

Currently you can get the info on ticket_Id and ticket_status but they can't express from which ticket they originated and thats a major need.

Will be waiting on ideas or responses.