QA Contact can't be edit with jira issue edit

[linup2011]

Describe the bug

when I tried to edit QA Contact for an issue with following command:
jira --debug issue edit ISSUE-1 --custom "QA-Contact"="jishi" --no-input
I got following warning and error:
⠋ Updating an issue...
Some custom fields are not configured and will be ignored. This will fail with error in the future release.
Please make sure that the passed custom fields are valid and configured accordingly in the config file.
Invalid custom fields used in the command: QA-Contact
⠙ Updating an issue...
Error:

• customfield_12315948: data was not an object

jira: Received unexpected response '400 Bad Request'.
Please check the parameters you supplied and try again.

Please provide following details

1. JiraCLI Version:

   (Version="v1.5.1", GitCommit="", CommitDate="", GoVersion="go1.20.11", Compiler="gc", Platform="linux/amd64")
   

2. Are you using Jira cloud or on-premise jira server?

   on-premise jira server
   

3. What operating system are you using? Also mention version.

   Fedora release 37 (Thirty Seven)
   

4. What terminal are you using? Also mention version.

   xterm-384-1.fc37.src.rpm
   

To Reproduce

Steps to reproduce the behavior:

1. jira --debug issue edit ISSUE-1 --custom "QA-Contact"="jishi" --no-input
2. See error
   ⠋ Updating an issue...
   Some custom fields are not configured and will be ignored. This will fail with error in the future release.
   Please make sure that the passed custom fields are valid and configured accordingly in the config file.
   Invalid custom fields used in the command: QA-Contact
   ⠙ Updating an issue...
   Error:

• customfield_12315948: data was not an object

jira: Received unexpected response '400 Bad Request'.
Please check the parameters you supplied and try again.

Expected behavior
the QA Contact can be modified

Screenshots

Additional context

the QA Contact is configured in the config.yml:
- name: QA Contact
key: customfield_12315948
schema:
datatype: user
- name: Product
key: customfield_12315949
schema:
datatype: option

[ankitpokhrel]

Hi @linup2011, you'd need to configure the field properly to make it work. Some details are outlined here.