I agree with Eileen https://jira.atlassian.com/browse/ATLAS-60?focusedId=3502321&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3502321.

We would not want the Atlas status to update automatically based on the Jira Epic. Atlas is for outward facing stakeholders while the Jira status is for internal.

I love the idea to add a block in Jira Automations https://jira.atlassian.com/browse/ATLAS-60?focusedId=3603736&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3603736. Being in a large company there are different stakeholders who like to gather project status in different ways. This has resulted in me needing to update Atlas and a custom field in my Jira epic to report the status of the project. It would be awesome if I were able to have the custom field of my epic sync with the linked Atlas project.

My automation would look something like.
If Custom field updated then post update in atlas and change the status in atlas.

+1 

Maybe a good compromise would be to add an "Update Atlas project" action block in automation. That way whoever chooses to do it automatically, can, and those who prefer to not have it, at least they can decide how or when. Does it make sense? Thank you!

We need this!

+1

This is indeed essential functionality to keep both "reporting" as well as "working" parts of the process in sync without extra manual steps.

We would not want this done (or at least not done automatically).

If the Epic workflow status was added as a separate field that would be great, but the project status should remain as a separate status for reporting to stakeholders and management and these statuses are completely different to our Jira Epic status.

Syncing the project status to the epic status removes important functionality for us and would actually completely dilute the purpose in our case for using Atlassian projects.

Absolutely +1 to this.