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

            Activity

              People

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

                Dates

                Created:
                Updated: