Help with automation integration permissions
Asked by Karoline Rezende Ramos:

Hello community!

I need your help.

We are doing an integration outside of jira automation, because we are having performance problems in our instance.

This automation consists of copying some attributes from the assets to custom jira fields, due to the issue of exporting and not bringing the values.

But these fields that need to be filled in by this automation are only on the preview screen, because they can't be edited and we run the risk of losing the original information.

But when we run this script, it returns an error because these fields are not on the editing screen.

Do you know how we can solve this?

Note: The user we are using has admin permission for the instance and not org.

Thank you very much in advance!

![Captura de Tela 2024-01-04 a?s 17.03.06.png](/t5/image/serverpage/image-id/299437iBF837317ECF7975D/image-size/large?v=v2&px=999 "Captura de Tela 2024-01-04 a?s 17.03.06.png")


Answers:
author: Gabriel Rodrigues
body: Hi Karoline

One approach that might work involves creating a self-reflecting transition with a transition screen that contains the field you want to update. Then, instead of making a request to update the issue, you would perform a request to transition the issue, as documented here: <https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-transitions-post>. In the request, you can fill the fields within the transition screen. Please note that I haven't tested this method.

If this doesn't work, I think that another solution for programatically editing the value of an issue's field that is not present in the Edit Screen is to utilize the overrideScreenSecurity query parameter when using editing the issue using the REST API as described in [https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-pu](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-put)t. However, according to the documentation, this option is restricted to usage within the context of Connect and Forge apps.

With that being said, another approach would involve creating a Forge app with a webhook component that serves as a proxy for your update requests. In this setup, you would send a request to the Forge app's webhook rather than the Jira API. Internally, the app would then route your request to the Jira API using its own permission.

I know that there are some apps that follow a similar concept, such as those that provide instance-like rest api keys (API Key Manager for Jira for instance), but since I've not used them I'm not sure if they allow the usage of overrideScreenSecurity query param.


author: Marc - Devoteam
body: Hi [@Karoline Rezende Ramos](/t5/user/viewprofilepage/user-id/4342260)

The message states the the Custom Field that needs to be set is not on the screen used for all or a specific issue type on the project with the KEY auto.

If you are able to access the project details of the project with key AUTO, you can see the issue type screen scheme and it's related screen scheme(s) and scheme(s)

The the screens and add the Custom Field with ID 18909.

[Find Custom Field by ID](https://confluence.atlassian.com/jirakb/how-to-find-any-custom-field-s-ids-744522503.html)


Tags: cloud

jira-service-management

jira-service-management-cloud