Make 'BasedOn' custom field option works with custom fields with autocomplete type

[danpoltawski]

Previously this option didn't do anything when a custom field was based on an field which set to the autocomplete type.

Fixes https://rt.bestpractical.com/Ticket/Display.html?id=37524

There maybe more elaborate solutions to prevent this JS firing when the autocomplete is 'in progress', but I went for the minimal approach.

Testing instructions:

• Make custom field 'Customer' with type 'Enter one value with autocompletion'
• Set some values for the Customer ('Customer 1', 'Customer 2')
• Make another Custom field 'Service' with type 'Select one value'
• Set the Service custom field to be Based on 'Customer'
• Add some values for the Service with the Category set to one of the customers, e.g.:

* Ensure both custom fields are applied to a queue and observe the behaviour on the create ticket page

Before this patch:
'Service' was always set to 'Nothing Selected'

After this patch:
The correct values are chosen in the Selection dropdown

[danpoltawski]

Is RT a dead project?

[johnsonjh]

(A bit off-topic, and not related to the issue at hand, but …)

This month, excluding merges, 7 authors have pushed 77 commits to stable and 118 commits to all branches. On stable, 196 files have changed and there have been 5,580 additions and 670 deletions.

RT is is a highly active project …

[danpoltawski]

A bit of a performative comment by me which I apologise for. But its a bit depressing to spend time on what seems like a simple fix, with clear testing instructions and have no feedback or even a comment to say we dont take contributions?

Then wondering whats been worked on and look RT bug tracker and see its full of spam thats been around for months:

I've got some more bugs to investigate and report and hopefully fix, but its difficult to motivate myself to look into them when seeing this.