-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
2
-
Severity 3 - Minor
-
Issue Summary
This is reproducible on Data Center: yes
Steps to Reproduce
- setup a webhook in JSM with a trigger for "issue created" and any testing endpoint where you will be able to catch and review the payload
- Create a new JSM issue to trigger the webhook
- The StatusCategory.name sent to the test endpoint will not match the StatusCatory name in the endpoint listed as the value for "Self"
Expected Results
The expected result is that the statusCategory matches, and the correct value of "To Do" is sent in the webhook
Actual Results
Example:
Here is the statusCategory object sent to the endpoint in my test:
"statusCategory":{"self":"https://johnmc.atlassian.net/rest/api/2/statuscategory/2","id":2,"key":"new","colorName":"blue-gray","name":"New"}}
as you can see the name is: "New"
however, when I go to the endpoint listed in that object for "self": https://johnmc.atlassian.net/rest/api/2/statuscategory/2 then I will see that "Name" has a value of "To Do" - which is the correct value.
Same as issue here, which was never fixed: https://jira.atlassian.com/browse/JRACLOUD-75717
Workaround
N/A
- duplicates
-
JRACLOUD-75717 Jira sending incorrect statuscategory in payload when closing tickets
-
- Closed
-