Uploaded image for project: 'Atlas'
  1. Atlas
  2. ATLAS-60

Automatically update Atlas project status when a tracked Jira EPIC status is updated

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      I created and tracked the projects at Atlas. These projects also have the tracked Jira EPIC. We want the Atlas status automatically updated when the tracked Jira EPIC status is updated or changed. This will streamline the update process and save the manual update effort.

            [ATLAS-60] Automatically update Atlas project status when a tracked Jira EPIC status is updated

            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.

            Derek Thrasher added a comment - 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 

            Toni Martínez added a comment - +1 

            Nino D. added a comment -

            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!

            Nino D. added a comment - 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

            Diogo Alves added a comment - 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.

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

            Eileen McEneaney added a comment - - edited

            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.

            Eileen McEneaney added a comment - - edited 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.

            Barney Mullan-Gage added a comment - Absolutely +1 to this.

              Unassigned Unassigned
              60007b79107d Ivy Chan
              Votes:
              27 Vote for this issue
              Watchers:
              25 Start watching this issue

                Created:
                Updated: