Problem Currently, copying a ticket ID only copies that ID to the clipboard, without the associated conversation URL.
Request When copying a ticket ID, also copy the conversation URL simultaneously.
ADMIN RESPONSE
May 19, 2026
Your idea is now live and open for voting.
Guest
May 25, 2026
How are you using the ticket number and conversation URL today? Are you sharing these internally or externally? I'm using them internally, providing the Conversation URL without the ticket number leaves valuable data out of the message, and makes it harder to the recipient to find the ticket. The ticket number is copied to Slack, and then the Conversation URL is then added as a link to the ticket number so that the intended reader can, with one click, navigate to the ticket, without having to first open Front, and then search for the ticket. By offering the url within the ticket number improves the efficiency of the conversation. It could be offered as another link combination in the 'kaibab' menu below (or adjacent to) the current message URL.
I'd also like to vote for this change. It will streamline internal conversations that must link back to a Front ticket, reducing the number of clicks from 5 to 2 (not counting key strokes)!
How are you using the ticket number and conversation URL today? Are you sharing these internally or externally?
I'm using them internally, providing the Conversation URL without the ticket number leaves valuable data out of the message, and makes it harder to the recipient to find the ticket.
The ticket number is copied to Slack, and then the Conversation URL is then added as a link to the ticket number so that the intended reader can, with one click, navigate to the ticket, without having to first open Front, and then search for the ticket.
By offering the url within the ticket number improves the efficiency of the conversation. It could be offered as another link combination in the 'kaibab' menu below (or adjacent to) the current message URL.
How are you using the ticket number and conversation URL today? Are you sharing these internally or externally?
I'd also like to vote for this change. It will streamline internal conversations that must link back to a Front ticket, reducing the number of clicks from 5 to 2 (not counting key strokes)!
This should already be a key product feature. We waste so much time having to separately copy each.
It is disappointing it doesn't do this already. The extra click and careful navigation to the conversation link seems very unnecessary.