Both merged support tickets should redirect to the new support ticket URL.
What happens now is one of the merged ticket's URL will show a "Ticket Not Found" when browsed.
We need a way to be able to search a ticket number (ID) after is was merge with another ticket. let's say me merge a ticket but then a customer calls us and ask about ticket number XXX that he opened - after this merger there is no ticket to be found....Or i'f we are keeping a note of a specific ticket to followup later - and this ticket have been merged, there is no way to find it again...Even in the ticket feedback comments report - if a ticket was merged after a customer already answered the feedback request, the ticket ID is "Not Found" and there is no way to find the ticket that the customer gave feedback about....So, We need a way to keep an pre merge ticket ID in the system and to be able to search it in the system and find the new ticket instead.Thanks!
We have 100s of ticket and often they are merged. Clients often forward us old copies of e-mails with ticket numbers and then we can't find the ticket, because since the case was opened it has now been merged with another one.
This behavior from WHMCS is completely unacceptable. I consider this very similar to data loss. Please fix it urgently. It's not good for business.
Posted 1 year ago... any news?
2 Years and still nothing.
Is such a feature request is very hard to implement?
We would love to have this issue fixed/
Sadly the WHMCS community as a whole tends to vote for superficial features like updated templates (which anyone could implement) as compared to actually useful functionality that nobody can implement except WHMCS devs. :(
Your point is...?
I agree with @jas8522. Everyone is getting lost in having a pretty cart instead of a billing application that improves on features. For example, the ability to just cancel invoices and the inability to produce real credit notes has haunted WHMCS for years. It just keep on looking pretty but it ain't really going forward. Let's hope this changes soon. (Been using WHMCS since 2007).
xxxmicrobexx, my point is two-fold:
1) I'm disappointed that a large part of the WHMCS community is favouring superficial features over core improvements. This is especially true given that as a whole we're probably all a fair bit more technically inclined than communities surrounding other software products. I thought there'd be more consideration going into the decisions of which feature to vote for in this requests system, and that the higher rated feature requests would be those surrounding functionality that no WHMCS admin can implement themselves.
2) It's even more disappointing to me that the WHMCS dev team isn't prioritizing core functionality over superficial things like themes. Particularly when they know very well that WHMCS admins can either build themes themselves, or pay for themes from WHMCS theme developers (or even pay a designer to create an entirely custom them for them). There are many great WHMCS theme designers out there.
I would love to have features like the one in this very topic of discussion implemented, and it's likely that they would have been implemented years ago if the WHMCS dev team had placed developers on these requests rather than on new themes.
I'm very hopeful that now that the new 'six' theme is complete and the new order forms are done, the developers behind them will now be working on functionality like this.
Great news - finally the status of this feature request was set to "In Progress" .
I hope this will be implemented soon...
Thanks for taking the time to submit your feedback, comments and votes. I'm pleased to advise this has been implemented in v6.3.
Comments have been locked on this page!