Forge Application overrideScreenSecurity.

[Alan Oh]

Hi,

Objective: I have a hidden field called "syncId" this field shouldn't be in the issue details view therefore I need to use the overrideScreenSecurity to populate the field.

I have tested using Scriptrunner the PUT method is fine, but when I tested it with forge it says that I have to have the Browse Project permission and to do it I also need to be JIRA Admin.

I have Added myself in my own instance as a JIRA Admin and ensure that I also have the browse and edit premission to perform the action.

I tried the same code with fields that are in the Screen Scheme but when the fields are not in the screen scheme or any screen It just keep throw 403. 

Error Message recieved
"Connect app users with "admin" permission and Forge apps acting on behalf of users with ADMINISTER permission can override screen security."

what could be the problem ?

Code Src index.jsx
------------

------------

YML file:

------------
permissions:
scopes:
- read:jira-user
- read:jira-work
- write:jira-work

------------

If anyone have any idea of what is going on please help me, thanks I have been stuck with this issue for a week now.

regards,

Alan.

[Alan Oh · Accepted solution]

Hi All,

I hope this helps those who have encountered this issue or want to use overrideScreenSecurity.

I have solved this by:

Changing a little of my code to use asApp() instead of asUser() also including. ALL the manage, read and write permission scope in to the yml file. I believe the attachment can help you get the answers you are looking for as well.

I have deployed my code and it is functioning as it should be.

[Wortho]

I finally got this working thanks for this snippet. For anyone that is struggling, you cannot do this on create new issue (despite the doco saying you can). Create the issue and then do an update to the custom field as shown here and it works in /api/3 too.

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Your Forge application is not logging in with a user who has permissions in that project.

[Alan Oh]

Hi Nic,

So that means, I have to add an Authroization in the header ?
I tried with Basic and Bearer before doing it this way

headers : {

    'Content-Type' : 'application/json',

    'Accept' : 'application/json',

    'Authroization': 'Basic <base64Token> or Bearer <base64Token>'

}

so the base64Token format is email@token ? 

Thanks for assisting in this matter

[Alan Oh]

please advise

[Alan Oh]

Hi Nic,

After some checking in the atlassian admin site for my instance. All my users are set to administrators of the jira instance, my permissions are as administrators  and my 3 users have, Org admin, Site admin and Jira admin permissions. 
What is missing.

I do not understand what am I doing wrong. Is it possible to provide me with a snippet of the code so that I can debug my code and perform the workaround. 
Thank you so much for assisting in this matter.

Regards,
Alan

[Nic Brough -Adaptavist-]

Admin rights mean admin, they do not mean you have any access to the projects.  Check that your users have browse project, and edit rights in it as well.

[YY Brother]

Hi Nic, I didn't get what you meant either. Could you please explain it more details about your suggested solution?