Hi,
It has been detected that the assignment of "Assigned to" and "Assignment group" fields is not working as expected during vulnerability ticket (VIT) creation through the API . We are supplying the correct "Assigned to" data and no "Assignment group" is supplied, as it is not mandatory, and the expected result is a VIT ticket with the "Assigned to" filled with the data supplied and no "Assignment group" assigned.
The problem is that we are obtaining two different results:
1. The automation tries to assign the "Assigned to" first, assigns it and then checks if "Assignment group" was supplied. As it was not supplied, by default is adding a specific group
2. The automation tries to assign the "Assignment group" first, as no group was provided it adds a specific group, then tries to assign the "Assigned to" and how the person doesn't belong to that group, the "Assigned to" field remains empty.
In addition, the rule of assigning a specific group as "Assignment group" should only be applied when no "Assignment group" and no "Assigned to" are supplied, if "Assigned to" is provided, that rule shouldn't be executed.
Please suggest what could be behind this issue.
