I've got here a case where the user prematurely upgraded to Mojave in violation to our policy. In addition, I do now see no more management options for the client device but statistics exist and are coming in. Is there any way I could remotely promote the old status again so that the device becomes fully manageable? Screenshot attached
Since Mojave is still in beta Jamf doesn't technically support it yet. I know on my test machine not only are management options lacking but Self Service and all Jamf app's don't launch. I would pull back the machine and wipe it until Jamf releases a version that is compatible with Mojave. I also put Install macOS Mojave.app as a restricted software so people can't try to upgrade.
The only reason a user should have a notification to install Mojave is if they installed the beta profile. All the restricted software does is block when they launch the Mojave Installer.app. Meaning users may still be prompted once Mojave comes out to install it, but once the installer launches it will quit and I have it delete the installer.
We have had success with 10.7.0 and Mojave. The changelog for 10.7.1 doesn't show much and it looks like it implements official support for new configuration profiles introduced in 10.7.0.
With that said, the only major issue in ur testing was Self Service not working, and that was resolved with 10.7.0. Mojave gets 0 day support from our group because our existing processes and policies in 10.13 have all worked without issue.