Autotask: Option to add charges to an existing ticket when creating a fulfillment ticket

Description:

When creating a fulfillment ticket from a won quote, we currently always create a new Autotask ticket. For teams where the original request came in as a support ticket, this results in two separate tickets for the same job: the original (which holds all work history, notes, and time entries) and the newly created fulfillment ticket (which holds the charges).

We'd like to offer the user a choice at the point of ticket creation, similar to how the contract selection works today: either create a new ticket, or add the charges to an existing ticket linked to the opportunity.

Proposed behaviour:

When clicking "Create Ticket" on a won quote, present the user with two options:

• Create a new ticket (current behaviour, remains default)

• Add to existing ticket, showing a list of tickets already linked to the opportunity for the user to select from

Why:

MSPs that receive hardware requests through support rather than through a dedicated sales pipeline need the charges to land on the pre-existing ticket so that all work history, notes, and charges stay in one place. A new ticket forces manual reconciliation between two records for the same job.