When the display name of a custom field is passed into the fields parameter of search_issues(), the field name is correctly mapped to the internal Jira field name when placing the search request. However, afterwards the field values are only mapped back to the display name in the raw attribute of issues, which means that calling get_field() on one of the returned issues with the displayed field name will raise an AttributeError exception.
Bug summary
When the display name of a custom field is passed into the
fields
parameter ofsearch_issues()
, the field name is correctly mapped to the internal Jira field name when placing the search request. However, afterwards the field values are only mapped back to the display name in theraw
attribute of issues, which means that callingget_field()
on one of the returned issues with the displayed field name will raise anAttributeError
exception.Is there an existing issue for this?
Jira Instance type
Jira Server or Data Center (Self-hosted)
Jira instance version
8.20.11
jira-python version
3.5.2
Python Interpreter version
3.9.6
Which operating systems have you used?
Reproduction steps
1. Given a Jira client instance
2. Call
search_issues()
with a custom field.3. Try to call
get_field()
on one of the returned issues.Stack trace
Expected behaviour
Value of custom field would be returned.
Additional Context
No response