Issue exists in 2.7. Solution requires changing the logic used to generate agents from user records. The simplest method would be to name the agent after the username, since that already has to be unique. Recommend changing priority to minor, adding the solution, and changing to ready for implementation.
Could not reproduce, submitter confirmed that this is not a problem anymore. Close as done.
Not clear this behavior is incorrect, commented asking for clarification.
ANW-736
-
Getting issue details...STATUS
fixed the reorder issue.
Github issue to investigate removal of parent_name exists
Depending on Dev response, wait or abandon?
Cannot reproduce this issue, I have asked the reporter for reproduction steps.
Recommend we wait for more information.
From Christine: “For the 2.7.0 release we’ve now added a configuration option to the end of the Config file - AppConfig[:limit_csv_fields] . By default this is set to true, to limit the fields in those CSVs to selected columns on the screen. If you set it to false it will work the way it did previously”
Does 2.7.0 technically resolve this issue by allowing to revert to “old way”? If the case, I move to close this ticket for now.