Bifurcate the tickets of their end-clients in their Halo Ticketing portal

[Balakrishna Gudla]

Actually we are using JSM ticketing portal and our client using halo Ticketing portal. Cyas Tech wants some changes in our ticket subject so that they can bifurcate the tickets of their end-clients in their Halo Ticketing portal.
I have sent a test ticket to them, CT-1930: Ticket # [CATID:0064966] | SOC::Cyas Tech || Coastline Family Farms || Test Ticket
Waiting for Client
making the required changes in the subject, that is adding a double pipeline "SOC::Cyas Tech || Client Name || XXXXX". But this didn't work at their end. Instead they want the same change to be implemented in the ticket body.

[Marc - Devoteam · Accepted solution]

Hi @Balakrishna Gudla 

What is the exact issue, the other ticketing portal can't handle the information, simple text?

So that would be something to investigate with the support of that software?

Why would Atlassian be asked to make changes so that another software product (not theirs), is able to handle text from a field?