Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
1
-
Severity 3 - Minor
-
0
-
Description
Issue Summary
When webhook is sent for issue create with status other than default then the webhook payload contains changelog containing "old status"->"new status" while the "status" field contains information about "old status".
Steps to Reproduce
- Create webhook for issue create operation
- Create issue with destination status other than default one
- Inspect webhook payload, it will contain "status: default one" and changelog with status changed from "default one"->"destination status"
Expected Results
No changelog in the event (as create issue with different destination status is multi-step operation that consist of: separate create issue + separate transition issue - 2 webhooks should be triggered)
Actual Results
inconsistent changelog in the event payload (here the default status is "To Do" and the status for created issue is "In Progress"
"status": { "description": "", "name": "To Do", "id": "10003", "statusCategory": { "id": 2, "key": "new", "colorName": "blue-gray", "name": "New" } }, ... "changelog": { "id": "10017", "items": [ { "field": "status", "fieldtype": "jira", "fieldId": "status", "from": "10003", "fromString": "To Do", "to": "3", "toString": "In Progress" } ] }
Workaround
None - customer should disregard the changelog for status field for issue create webhooks and rely on separate issue_updated webhooks (from transition)
Attachments
Issue Links
- relates to
-
JRACLOUD-68855 The Status Category name is inconsistent between different services - It shows up correctly on REST Calls, but is registered incorrectly on Webhooks
- Gathering Impact
-
CES-16684 Loading...
- is caused by
-
CRANE-1833 Loading...