Currently, if I give additional field in JSON payload which is not present in create field, I am getting the following error in Postman:
"customfield_10436": "Field 'customfield_10436' cannot be set. It is not on the appropriate screen, or unknown."
Is there any possibility to have additional fields(not in the screen) in the payload without errors?
Unfortunately no. Here's a reference link from Atlassian :
https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/
The section
specify that your field must be on your screen to be editable.
I know that Atlassian is working on a way to add fields to a Request type even if they're not on the create screen (this is an early features I'm testing). This means that every fields are available and when you add one to a request type form, the field is added automatically to the "Create" screen. So maybe what you want to achieve could be possible in the future, but not now.
Hope this helps
Have a nice day
Frederic Chartrand
FMX Solutions - Gold Solution Partner
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.