Are you also turning on FileVault during your testing? If so, what you're seeing after restarting the computer is the FileVault login window not the macOS login window. You'll know it's the FileVault window because you authenticate first and then you see the progress bar as macOS starts.

By default, after you authenticate at the FileVault window, it will then pass your credentials to macOS and bypass the macOS or Jamf Connect login window and go straight to the end user's desktop. You can set the DenyLocal key's value to true to force the end user to also authenticate to the Jamf Connect login window. But that will be a double-login experience for them.

Hello, Yes we are using Filevault. So after 1 restart we see the Jamf Connect Login Window, After we sign in and restart again the Jamf connect login window disappears. We want to see the Jamf Connect Login Window disappear after 1 restart. 

Are you using Jamf Connect itself to turn on FileVault using the EnableFDE key? If so, Jamf Connect only turns on FileVault the first time someone authenticates at the Jamf Connect login window.

After your install and restart, Jamf Connect hasn't turned on FileVault yet because no one has authenticated using Jamf Connect.

You log in, which turns on FileVault, then you restart.

Then you see the FileVault login.

Until you've turned on FileVault using Jamf Connect, or manually in System Settings, or using something like a Jamf Connect policy, you'll continue to see the Jamf Connect login window.