Thanks for getting in touch! I can certainly see why you would want the parent project to show the correct status here. I ran a test to purposefully cause a success with warning in a child project, though it correctly set the same warning status on the
Deploy a Release step that deployed that child project. This was in my local instance running latest (2019.13.2) - can you let me know which version you’re currently running? It might simply require an upgrade to apply some recent changes we’ve made in this area.
If you’re already running latest, could you send through some additional information to give me a deeper look into what could be causing this? The information to help would be the task logs from the deployments of both the child and parent projects, and also the deployment process JSON from both projects (these JSON files can be downloaded from the overflow menu in your project’s deployment process page as shown below).
I look forward to hearing back and getting to the bottom of this one!