You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 POkey: customfield_10811schema:
datatype: user
e.g.
jira issue edit EXMP-1234 --custom assigned-po='{"name": "$(jira me)"}'Error: - customfield_10811: data was not an objectjira: Received unexpected response '400 '.Please check the parameters you supplied and try again.
The text was updated successfully, but these errors were encountered:
kwv
changed the title
How can I set custom fields on issue creation?
proposal for custom fields on issues
Mar 24, 2023
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
andMulti-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 ?
e.g.
The text was updated successfully, but these errors were encountered: