-
Bug
-
Resolution: Timed out
-
Low
-
1
-
Minor
-
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".
- is related to
-
JRACLOUD-76193 Updating the epic of a team-managed (formerly next-gen) issue does not fire any webhooks
-
- Closed
-
-
JRACLOUD-92532 Adding an issue to an epic in next-gen does not trigger an "issue updated" event
-
- Closed
-
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.