-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Work Item - Backend - Read
-
None
-
1
Currently API endpoint POST Bulk Fetch Changelogs
The changelog/bulkfetch API is designed to retrieve changelog entries for specified work items/issues. Each changelog entry typically includes a fieldId that allows for filtering. However, in some cases, a changelog entry might not have a fieldId, which can lead to unexpected results when attempting to filter by specific fields.
Changelog items sometimes lack a fieldId, which complicates filtering.
"items": [
{
"field": "project",
"fieldtype": "jira",
"fieldId": "project",
"from": "11XX",
"fromString": "Tk",
"to": "11554",
"toString": "Systems Mgmt"
},
{
"field": "Component",
"fieldtype": "jira",
"fieldId": "components",
"from": "10XX",
"fromString": "Knowledge Base"
},
{
"field": "Key",
"fieldtype": "jira",
"fromString": "TM-XX",
"toString": "BT-XX"
},
{
"field": "Component",
"fieldtype": "jira",
"fieldId": "components",
"to": "109XX",
"toString": "Knowledge Base"
},
{
"field": "Key",
"fieldtype": "jira",
"fromString": "TEST-1",
"toString": "EXAM-340"
} ]
This chnagelog hold FieldID
{ "field": "Component", "fieldtype": "jira", "fieldId": "components", "to": "109XX", "toString": "Knowledge Base" }
While below one would not hold :
{ "field": "Key", "fieldtype": "jira", "fromString": "TEST-1", "toString": "EXAM-340" }
Behaviour can be noticed with some of the system field such as Issue key.
Ask:
Please include fieldId for "key" field Type.