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

Adding an issue to an epic in next-gen does not trigger an "issue updated" event

    XMLWordPrintable

Details

    Description

      Issue Summary

      Currently, when an issue is added to an epic in next-gen, Jira fires the Issue Updated for the child issue, but not for the Epic Parent. This is causing only one automation rule to be triggered for the child but not for the epic, even though the Epic's history indicates that Epic Child was updated. 

      (Epics in classic are unaffected.)

      Steps to Reproduce

      1. Create an automation rule with an issue updated as a trigger event. 
      2. Add Issue to an Epic
      3. The rule is triggered once for the child, although the parent was updated as well. 

      Expected Results

      Adding Stories to Epics should trigger the rule for both issues. 

      Actual Results

      Only the Story throws the rule once. 

      Affected Components

      Epics in next-gen

      Automation for jira

      Workaround

      No workaround. 

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-75091 Changing the epic of an issue in a next-gen project does not result in jira:issue_updated webhook events

          • Low - Low priority issues
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-76193 Updating the epic of a team-managed (formerly next-gen) issue does not fire any webhooks

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JSWCLOUD-15973 Webhooks do not fire from adding issue to Epic

          • Low - Low priority issues
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JSWCLOUD-22498 Automation for Jira: Updating parent Epic field in next-gen project issues does not trigger "Issue Updated"

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. AUTO-569 Team Managed Projects: Copy from Parent and Epic does not work in the team-managed (Next-gen) project

          • Low - Low priority issues
          • Long Term Backlog

          ACJIRA-2088 Loading...

          Activity

            People

              Unassigned Unassigned
              jgonzalez2@atlassian.com Jose Luis Gonzalez 2
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: