Hi everyone,

I'd like to inform you that we've just enabled an endpoint to get all screens:

GET /rest/api/2/screens

It requires admin permission of calling user, and returns a list of all screens with their names and IDs.

This API is only available for Jira Cloud.

Sincerely,
Eve Stankiewicz
Product Manager for Jira Cloud Ecosytem

@Sachin: Many Thanks!

Jira Add-on - Copy.rar
PFA the zipped source code

@Sachin: Would you consider to provide the source for the full plugin? Regards, Jens

Hi Sachin,

Thanks for above code. I am sorry but could you please tell what is atlassian-plugin file? and where Can I find it?

Thanks and regards,
Pankaj

I am also eagerly waiting for this REST API. Meanwhile I have written a custom code which works:

package com.celigo.plugins.netsuiteJiraConnector.rest;

import com.atlassian.plugins.rest.common.security.AnonymousAllowed;

import javax.ws.rs.*;
import javax.ws.rs.core.MediaType;
import javax.ws.rs.core.Response;

import java.util.Collection;
import java.util.ArrayList;
import com.google.gson.Gson;
import java.lang.*;

import com.atlassian.jira.component.ComponentAccessor;
import com.atlassian.jira.issue.fields.screen.FieldScreenManager;
import com.atlassian.jira.issue.fields.screen.FieldScreen;

@Path("/list")
public class jiraConnectorforNetSuite {

@GET
@Produces(

)

public Response getMessage()

public static ArrayList<String> getFieldScreens() {
FieldScreenManager customFieldScreenManager = getCustomFieldScreenManager();
Collection<FieldScreen> screensList = customFieldScreenManager.getFieldScreens();
ArrayList<String> ScreenIds = new ArrayList<String>();
for (FieldScreen fieldScreen : screensList)

return ScreenIds;
}

private static FieldScreenManager getCustomFieldScreenManager()

}

And the configuration in atlassian-plugin file is like this:
<rest name="Screens" i18n-name-key="rest-resource.name" key="rest-resource" path="/screens" version="1.0">
<description key="rest-resource.description">Rest Resource Plugin to get Screens List</description>
</rest>

Why has this still not been resolved after a year and a half? The entire screen and field gathering part of the REST API is unusable without this.

Please fix this ASAP as it blocks a lot of crucial functionality in the REST API.

It's impossible to assign a screen schema when creating a project.
It's impossible to fetch a list of screens, or determine which screen schema is assigned to a project.

This missing piece of functionality prevents me from writing the migration script I need to make the jump to Jira.

Trying to do integrations for JIRA and using custom fields to add metadata onto issues in JIRA is currently also impossible to do entirely via the REST API because after adding a custom field via the API, there doesn't seem to be any way to then add it to a screen that is associated with a JIRA issue as well. But how on earth is one expected to get the screen id?

And a better question is: Why isn't this information on the actual issue itself when retrieving it from the REST API?

I agree. We have met this same problem with our AddOn for JIRA Cloud. Without this API, we aren't enable to check or correct if the screen/field is set correctly.

This bug is blocking !