How to get the current user using ScriptRunner Jira cloud and update a field using /rest/api/2/issue

Question

I am trying to update a field based on the current user using Script Runner Jira cloud as a post function of a workflow transition.

The script contains

def usr = get('/rest/api/2/myself').asObject(Map)
assert usr.status == 200

This returns the current user, I can use this to update a field using

def resp = put("/rest/api/2/issue/${issue.key}")
.queryString("overrideScreenSecurity", true)
.queryString("overrideEditableFlag", true)
.header("Content-Type", "application/json")
.body(updateDoc)
.asObject(Map)

The problem is that if the script is run as "current user", /rest/api/2/myself returns the current user, but the put call to /rest/api/2/issue/$(issue.key) fails, due to security/admin

nERROR: TSVCM-540: Connect app users with \"admin\" permission and Forge apps acting on behalf of users with ADMINISTER permission can override screen security."

However, if I run the script as ScriptRunner add-on the /rest/api/2/myself returns Script runner add on and not the current user that is executing the transition resulting in post process and the put(/rest/api/2/issue/${issuekey} executes without errors

So, how do I get current user and update a field using the put function.

Alejandro Reyes · Answer

Yeah, but let's put this example.

I need, on one specific transition, to add the current user on a User Picker customfield AND copy this value into a linked issue of another project which the current user does not have access (nor it should).

The problem is that I cannot do 2 different postfunctions that execute this because the changes made by the first postfunction should be sent by the second one and SR cloud acts async which will execute both post functions at the same time, which will may send or not the value and make the PF not work at all as intended.

How could we get the initiatior of the transition without having to change the actor of the transition to "Current User" which will make the things not work. That's the issue here.

Fayaz Abdul_36gnrz · Answer

@Rajeev Joshi Did you solved this issue??

Jay Nelson · Answer

The situation I ran into for this was similar, however I used the ID of a user with Admin to then apply to a different user so that it ran as that "Super user" instead of the user on screen.