reference or linked tickets --

[raymond]

this idea is different than having Projects (master tickets) and sub-tickets... which should be way up in the development process

how about having a place to link associated tickets, similar to linking multiple tickets to assets (and hopefully soon, a way to link mulitple assets to tickets!). The idea is if a tech made a connection between two different tickets, they could link them as a reference link (it really doesn't need to be more than that at this point). A really good example of usage would be when a client opens multiple tickets... we could close the duplicate tickets with a reference back to the original (I understand that there is a ticket merge feature but quite simply, it's not useable at all).

Another example would be if a tech worked a problem and in the process found the solution was already implemented in another ticket. They could simply reference the other ticket for troubleshooting purposes.

thanks --

//ray

[nattivillin]

Re: reference or linked tickets --

We created a ticket tab called QB so we could keep up with the QB invoice that is associated with each ticket.

The ability to link other things inside of CommitCRM would be very helpful. Especially for multiple tickets and assets!

[Support Team]

Re: reference or linked tickets --

@nattivillin - this is an interesting solution. Thank you for sharing.
@ray - maybe you can indeed add a custom tab for Tickets and place as many fields as needed to 'link' objects in RangerMSP using the special 'Linked Object' field type (available in the drop down when adding new custom fields). While not the same it may provide you with some kind of a solution - now.