-
Bug
-
Resolution: Unresolved
-
Medium
-
7
-
Severity 3 - Minor
-
Issue Summary
"Issue created" webhooks occasionally are missing the Request Type field (when it should be present).
This is playing havoc with some Automation Rules that rely on the field.
Steps to Reproduce
Unfortunately, this part is still eluding us
Expected Results
Request Type field is always present if it exists.
Actual Results
Request type field is null.
Workaround
For Automation, re-fetching the issue details as the first step cane work and makes the data is available for the rest of the rule
[JRACLOUD-83068] Create Issue webhook does not always contain the request type field
Support reference count | Original: 6 | New: 7 |
Priority | Original: Low [ 4 ] | New: Medium [ 3 ] |
Last Update On | New: 11/Mar/2025 [ 2025-03-11 ] | |
Status | Original: Gathering Impact [ 12072 ] | New: Gathering Impact [ 12072 ] |
Component/s | New: Issue View - Custom Fields [ 77931 ] | |
Component/s | New: Issue - Backend - Create [ 73898 ] | |
Was this caused by a recent change? | New: No [ 19032 ] | |
Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
Support reference count | Original: 4 | New: 6 |
Resolution | Original: Timed out [ 10 ] | |
Status | Original: Closed [ 6 ] | New: Needs Triage [ 10030 ] |
Resolution | New: Timed out [ 10 ] | |
Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
Labels | New: timeout-bulk-close202502 |
Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
Support reference count | New: 4 |