Hey Guys,

Any update on this? We are very much interested use REST API to get screenID.

I've created a simple plugin that accomplishes this. You may build it from source or simple download the .obr file and install it via the Universal Plugin Manager.

It doesn't do anything fancy – I offer it under no guarantee or warranty. Install at your own discretion. Pull Requests accepted.

https://bitbucket.org/sfbehnke/field-screen-helper/src/master/

Hey guys,

I added this functionality into my plugin Extender for Jira

Best regards
AL

Another request to be able to get screen id from REST API. 

Reason is that so that we can add custom fields but this requires screen id (and tab id) values.

Looking for a way to compare screens/issue types across multiple Issue Type Screen Schemes. As noted, for a project we can get the issue types but cannot get the chain of:

• Project Issue Type --> Project Issue Type Screen Scheme --> Screen Scheme (default, view, edit, create) 

@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 !

There should be some way to "navigate" results so we know what IDs to use for screens - tabs - fields via the JIRA REST API as it is currently laid out this is not possible.
https://jirahost/jira/rest/api/2/screens/*10811*/tabs/*10913*/fields
Thanks!

It's a missing area of the REST API. Call it bug or suggestion, it's not documented and really annoying.

Hi Jaime,

I don't think so this is suggestion. This is a bug. You are providing us availableFields, tabs, fields of tabs etc using REST but you are not providing screenid without which we can not get all these things. It is something like you are service ice-cream with out a cup.

Hi hiren_880,

Thank you for reporting this, I have changed the issue type to Suggestion as this is something that is something that our current REST Api (https://docs.atlassian.com/jira/REST/latest/) doesn't support, and we would need to include it.

All the best,

Jaime.