Issue Summary

Jira Service Management (JSM) sends the statuscategory as "Complete" in the outgoing payload when  closing or resolving tickets.

Even though the statuscategory is configured as "Done" for the status "Close" or "Resolve", the statuscategory is getting sent as "Complete".

The legacy automation sends the correct statuscategories in the payload. The system webhooks send the incorrect payload.

Steps to Reproduce

1. Create a Status called "Resolved" and assign it to statuscategory "Done".
2. Create a ticket and mark the status of the ticket to "Resolved"
3. Check the outgoing payload sent from JSM. The statuscategory has the value "Complete"

Expected Results

The statuscategory should be having the value "Done". Payload from a legacy automation showing the correct values are shown below.

#### Payload from Legacy Automation showing the correct values #### "statusCategory": { "self": "https://uravi-stg-test.jira-dev.com/rest/api/2/statuscategory/3", "id": 3, "key": "done", "colorName": "green", "name": "Done" }

Actual Results

The statuscategory has the value "Complete". This value is no where configured in the JSM setup. Sample payload shown below.

				
#### payload from system webhooks showing incorrect statuscategory ####
"statusCategory": {
					"self": "https://uravi-stg-test.jira-dev.com/rest/api/2/statuscategory/3",
					"id": 3,
					"key": "done",
					"colorName": "green",
					"name": "Complete"
				}

Workaround

Use the webhooks method provided via Legacy Automation under Project Settings > Automation. Payload sent via Legacy Automation puts the correct statuscategory.