Issue Summary

Object not having connectedTickets() is returning the same object as Object having connectedTickets() in some cases.

Consider we have two tickets: TK-1, TK-2. In this scenario, both TK1 and TK2 has a custom field that is linked to Obj1.

• TK-1 -> Obj1
• TK-2 -> Obj1

When running the AQL query:
Object having connectedTickets(Key = "TK-1"), obj1 is returned. 
However, when running the AQL:
Object not having connectedTickets(Key = "TK-1"), obj1 is also returned. This might because we consider "TK-2 -> Obj1" as not having connectedTickets to TK-1

Steps to Reproduce

1. Create a custom field
2. Create two tickets and assign the same object on that custom filed.
3. Go to the object in Assets page
4. Search AQL
   • Object not having connectedTickets(Key = "${Ticket1}")
   • Object having connectedTickets(Key = "${Ticket1}")
5. Those 2 AQLs will return the same object

Expected Results

Object not having connectedTickets(Key = "${Ticket1}") will not return objects that has ticket connection to Ticket1

Actual Results

Object that has ticket connection to Ticket1 is returned

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available