Again DC Customers seem to be only second class customers for Atlassian. Shame on them.

+1, it seems that Cloud V3 cover pretty much all that is missing in v2 ?

+1

It would be really useful for all Jira DC admins if Atlassian could align the REST v2 to the Cloud v3 https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#about 

Definitely.  We have what we've called Confidential and non-Confidential project types, and we are not able to update Issue type scheme on the fly due to this.  Manual update by support team is error prone and causing us data integrity issues.

Seriously? I can create a new Workflow Scheme in the API but can't associate it to a workflow... What on earth?

Can someone please explain the usefulness of even putting Workflow Scheme in the API and then rendering it usassignable? Why even bother... 

Create, manage and assign field configs to projects would be amazing to complete being able to create a project with separate schemes using the API

That would help immensely not to have to teach helpdesk all the backend admin sections in Jira. Which would also eliminate errors from unexperienced people that don't fully understand yet the implications of their actions, but they still have almost full admin rights in Jira in order to just create and manage projects, and it will also allow to scale projects creation to a wider audience not putting the overhead to small teams that know how to admin Jira.

Also from an admin perspective being able to clean up any scheme that is not used would help building an automate clean up process. The way we can't search for schemes and entities not tighten to a project already, makes administering Jira at scale very difficult

We have thousands of custom fields and I need a way to create a field config that hides most of them, without spending days clicking Hide on an incredibly long screen.

Would be real nice to have this implemented. Thanks.

Definitely would be useful. We use an external system that integrates with Jira to routinely perform validation checks to ensure that the system expectations of the shared Jira environment have not changed. There are quite a few configuration datapoints that are similarly hidden from the current REST APIs.