Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-22498

Automation for Jira: Updating parent Epic field in next-gen project issues does not trigger "Issue Updated"

      Issue Summary

      Automation rules which are configured with the trigger "Issue updated" does not run when the parent Epic field is updated is next-gen projects.

      From the issue history, we can confirm the change but the automation rule is not triggered.

      Steps to Reproduce

      1. Create an automation rule with the trigger "Issue Updated"
      3. Create a next-gen project and create an issue of type Epic
      2.  Create a standard issue (Task, Story, etc) and update the Parent Epic.

      Expected Results

      As the Parent Epic was updated, automation rule with the trigger "Issue Updated" should execute.

      Actual Results

      Automation rule is not triggered

      Workaround

      Current workaround is to create child tasks using "Add a child task" only which can then trigger "Issue Created".

            [JSWCLOUD-22498] Automation for Jira: Updating parent Epic field in next-gen project issues does not trigger "Issue Updated"

            Dylan added a comment -

            Hi all,

            Thank you for raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved.

            To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            Dylan added a comment - Hi all, Thank you for raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

              Unassigned Unassigned
              b678926ca497 Bopanna
              Affected customers:
              16 This affects my team
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: