Bug summary

I believe your commit in https://github.com/pycontribs/jira/pull/2334/files#diff-442d14b20d591afd0c3de830d2803e30d4816eedc708f9ad129316aa7e5a4a7cR3714 is causing an unexpected bug

Specifically, fields supports a list of strings but the logic that was added to enhanced_search_issues() empties this argument if a list is actually provided:

 if fields is None: fields = ["*all"] elif fields and isinstance(fields, str): fields = fields.split(",") else: # this is required only for mypy validation fields = [] 

Is there an existing issue for this?

• I have searched the existing issues

Jira Instance type

Jira Cloud (Hosted by Atlassian)

Jira instance version

No response

jira-python version

3.10.0

Python Interpreter version

3.12

Which operating systems have you used?

• Linux
• macOS
• Windows

Reproduction steps

I can access `fields` object if I use jira v3.8.0, if I manually access the new API outside of this library and if I use a comma separated list of values to pass to `enhanced_search_issues()`, but not if I provide a list of values

Stack trace

N/A

Expected behaviour

something along the lines of:

 if fields is None: fields = ["*all"] elif fields and isinstance(fields, str): fields = fields.split(",") elif fields and isinstance(fields, list): fields = fields else: # this is required only for mypy validation fields = [] 

where you accept fields being a list and don't just empty it

Additional Context

No response