proposal for custom fields on issues

[Kris Vandesteeg]

Discussed in #346

^{Originally posted by ankitpokhrel April 20, 2022}
Jira supports a wide variety of datatypes when creating a custom field. Out of all formats mentioned in the Jira doc, the tool right now doesn't support Cascading select custom field, Single-user picker custom field and Multi-user picker custom field. Support for these missing types will be added based on the request and the usecase.

---

For fields with unsupported/complex datatypes, would it be possible to allow the object representation to be passed in ?

    - name: Assigned PO
      key: customfield_10811
      schema:
        datatype: user

e.g.

jira issue edit EXMP-1234 --custom assigned-po='{"name": "$(jira me)"}'


Error:
  - customfield_10811: data was not an object

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

[Ankit]

Hi @kwv, I am considering this to be an option, will check to see if its doable in the near future.

[Reuben Taylor]

Hey - with my companies setup I'm unable to create Bug type issues since they require a custom field in the form of a Single-user picker custom field.

I really like using this cli but this makes it difficult for me to use

[gzliew]

@ankitpokhrel is there a workaround for this? maybe I can edit the source 🤔