-
Bug
-
Resolution: Low Engagement
-
Medium (View bug fix roadmap)
-
None
-
8.10.0
-
None
-
8.1
-
1
-
0
-
Issue Summary
When adding an issue to an Epic (either from JIRA or from JIRA Agile) doesn't trigger the Issue Updated event on the Epic and therefore it doesn't notify anyone.
Steps to Reproduce
- Add an issue to an Epic
Expected Results
Jira triggers the Issue Updated event.
Actual Results
Jira doesn't trigger the Issue Updated event.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- is cloned from
-
-
- Closed
-
- is related to
-
JRASERVER-8505 Add a new "Issue Linked" event for listeners to respond to
- Future Consideration
[JSWSERVER-20642] Adding an issue to an Epic doesn't trigger the Issue Updated event
| Resolution | New: Low Engagement [ 10300 ] | |
| Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
| Labels | Original: affects-cloud affects-server | New: affects-cloud affects-server cleanup-seos-fy25 |
| UIS | Original: 2 | New: 0 |
| UIS | Original: 0 | New: 2 |
| UIS | Original: 1 | New: 0 |
| Introduced in Version | Original: 6.03 | New: 8.1 |
| Description |
Original:
When adding an issue to an Epic (either from JIRA or from JIRA Agile) doesn't trigger the *Issue Updated* event on the Epic and therefore it doesn't notify anyone.
|
New:
h3. Issue Summary
When adding an issue to an Epic (either from JIRA or from JIRA Agile) doesn't trigger the *Issue Updated* event on the Epic and therefore it doesn't notify anyone. h3. Steps to Reproduce # Add an issue to an Epic h3. Expected Results Jira triggers the *Issue Updated* event. h3. Actual Results Jira doesn't trigger the *Issue Updated* event. h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
| Affects Version/s | New: 8.10.0 [ 91808 ] | |
| Affects Version/s | Original: 6.3.11 [ 38908 ] |
| UIS | New: 1 |
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center