-
Bug
-
Resolution: Fixed
-
Low (View bug fix roadmap)
-
7.2.8, 7.2.15, 8.0.0, 7.6.14, 8.4.0, 7.13.5, 8.3.3
-
7.02
-
3
-
8
-
NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.
When updating the Epic Link field of an issue no webhook event is fired.
To reproduce:
Enable all webhooks for issues - no custom JQL
Create an Epic (webhook fired)
Create a Story with no Epic Link (webhook fired)
Edit Story to add Epic Link (no webhook fired)
Expected behavior:
A webhook event of type jira:issue_updated would be fired for the Story
- derived from
-
JSWSERVER-12299 Change in Epic Link field does not trigger listener
-
- Closed
-
- duplicates
-
JSWCLOUD-15973 Webhooks do not fire from adding issue to Epic
-
- Closed
-
- relates to
-
JSWCLOUD-11149 Webhook not fired when updating Epic Link of an issue
-
- Closed
-
-
MNSTR-3204 You do not have permission to view this issue
Form Name |
---|
[JSWSERVER-11149] Webhook not fired when updating Epic Link of an issue
Fixed in Enterprise Release/s | New: [Download 8.5|https://confluence.atlassian.com/enterprise/atlassian-enterprise-releases-948227420.html] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
UIS | Original: 5 | New: 8 |
UIS | Original: 8 | New: 5 |
UIS | Original: 10 | New: 8 |
Fix Version/s | New: 8.4.2 [ 89301 ] | |
Fix Version/s | Original: 8.4.1 [ 88910 ] |
Fix Version/s | New: 8.5.0 [ 87495 ] | |
Fix Version/s | New: 8.4.1 [ 88910 ] |
Status | Original: In Review [ 10051 ] | New: Waiting for Release [ 12075 ] |
Current Status |
Original:
{panel:title=Atlassian Update – 28-11-2018 | borderStyle=solid|borderColor=#ebf2f9 | titleBGColor=#ebf2f9 | bgColor=#ffffff}
Hi everyone, We have recently reviewed this issue and the overall interest in the problem. Since the issue hasn't collected votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future, i.e. in next 6 months. We would aim to address the problem within the next 6-9 months or so, yet please do not consider this a deadline to fix the bug, but rather as an estimated timeline. While our decision to prioritise this in distant timeline might be frustrating, we want to be clear in managing your expectations. The Jira team is [focusing on issues|https://jira.atlassian.com/secure/RapidBoard.jspa?rapidView=2418&useStoredSettings=true] that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the [Atlassian Bugfix Policy|https://confluence.atlassian.com/support/atlassian-bug-fixing-policy-201294573.html] for more details. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ignat Alexeyenko Jira Bugmaster {panel} |
Remote Link | New: This issue links to "MNSTR-3204 (Bulldog)" [ 448312 ] |