It seems that in order to set a field through the REST API the field must appear on the screen for creating an issue. Otherwise you get this type of error: Field 'fixVersions' cannot be set. It is not on the appropriate screen, or unknown. It seems strange to me that the API should be limited by the UI since often the purpose of using the API is to perform things that the UI is not capable of. Is it possible to access a field without it being visible to users? For example if I want to have a custom field that is only accessible through the API but hidden from users (for cosmetic rather than security reasons), is it possible to achieve this?

Community
Q&A
Jira
Questions
Is JIRA REST API really limited by visible fields?

Is it possible to show epics as cards with their workflow status on the Kanban board in Next-gen?

I want to display the Epics in the same way as we do the stories on our Kanban board in Jira Next-Gen. I know how to setup the view in classic, but I was not sure if the option is available in Next-Gen. Next-Gen meets all of our other needs, but this is a pivotal view that seems to be missing and I am hoping it is user error. Thank you in advance for answer and support on this!

2 answers

1 accepted

1 vote

Answer accepted

No, REST respects the settings in the UI.

The purpose of the REST API is to allow you to do things inside the application - it would be a nightmare to say to users "hey, here's a UI, but if you use REST, you can bypass all the configuration and settings and do what the heck you like". You might as well throw away all your control and tracking, along with the web interface. You really do need REST to respect the UI.

You could play some javascript tricks - hide the field with a bit of javascript embedded on the page - the field will still be shown to the user's browser, but the javascript will remove it. REST will get the whole page like the browser, but ignore the javascript.