Hey @shsalam !
We worked on making it clearer for end users indeed, because our previous naming was not so clear for a human being 
The new naming convention for namespaces / applications / jobs / dbs now includes the service sanitized name.
Given an app called tetris:
Previously => app-z3f27e6ba-648ff5b668 with this schema (app-z<qovery_project_id>-<qovery_application_id>)
Now => app-z648ff5b668-tetris with this schema (app-z<qovery_application_id>-<sanitizied_app_name>).
This new naming applies only on new environments, created after this feature has been released. If you are not seeing it, odds are your env was created before, so you can create a new one (or clone existing ones).
Service / env renames won’t be reflected, names will remains the sames.
Checkout [RELEASED] Naming update on Kubernetes resources for more details.
Cheers