nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Change issue reporter with ScriptRunner

AccessHolding

Hi Community,

I am completely new regarding to ScriptRunner topics and need some good start. In the end I want to perform a simple postfunction as soon as a issue was created. I have an customer field "On behalf of" there customers could create a issue for their colleagues.

My intention is, as soon as this field "On behalf of" != null the system field creator/reporter should be replaced. "On behalf of" is a single-user-picker field as well. A business case could be that a colleague has currently no time to create an issue by themself and another colleagues jumps in without being notified the whole time.

If you have an idea by any chance I would appreciate it.

Best,

Kristian

Accepted answers

Mark Markov

Hello,

As @Danyal Iqbal says scriptrunner documentation is good place to start.

Second one is this community, there are tons of quiestions and answers with code, just google it

And for your example you can use this code in posfunction

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.MutableIssue

MutableIssue issue = ComponentAccessor.getIssueManager().getIssueByCurrentKey("")

def onbehalfCustomField = ComponentAccessor.getCustomFieldManager().getCustomFieldObjectByName("On behalf of")
def onbehalfValue = issue.getCustomFieldValue(onbehalfCustomField)
if (onbehalfValue){
    issue.setReporter(onbehalfValue)
}

And do not forget to place this postfunction right befoge "Update change history for an issue and store the issue in the database."

All comments

Danyal Iqbal

a good place to start would be the script runner documentation

and the 101 code example below:

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.Issue


def currentAppUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser()


issue.setReporter(currentAppUser);

Mark Markov

Hello,

As @Danyal Iqbal says scriptrunner documentation is good place to start.

Second one is this community, there are tons of quiestions and answers with code, just google it

And for your example you can use this code in posfunction

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.MutableIssue

MutableIssue issue = ComponentAccessor.getIssueManager().getIssueByCurrentKey("")

def onbehalfCustomField = ComponentAccessor.getCustomFieldManager().getCustomFieldObjectByName("On behalf of")
def onbehalfValue = issue.getCustomFieldValue(onbehalfCustomField)
if (onbehalfValue){
    issue.setReporter(onbehalfValue)
}

And do not forget to place this postfunction right befoge "Update change history for an issue and store the issue in the database."

AccessHolding

Hi Mark,

Just quickly two different questions.

issue.setReporter(onbehalfValue)

I receive an error [Static type checking] - cannot find matching method. I also checked the API which is actually fine with this function. You mentioned

And do not forget to place this postfunction right befoge "Update change history for an issue and store the issue in the database."

Means I cant do this post-function right after "create", before a customized status steps in? Because I actually need this before any ticket reaches the first status. I am asking because the "Update change history for an issue and store the issue in the databse" action is not mentioned during the first post-function after "create".

Best,

Kristian

Mark Markov

Hi Kristian,

This is static type checking error, you can ignore that. This is happens because method getCustomFieldValue defined return object value (actually it can returns Options object Application User object, String object), so compiler doesnt know which one returns and set this error, but we know that from User picker field it will return Application User.

Yes, you can place this after create (main requiriment is that issue object must be created), but if something esle will change reporter after, it will not work.

AccessHolding

Hi Mark,

Thanks for your help and time.

The script runs now for each new created issue but unfortunately the reporter doesn´t change. Maybe I did something wrong from the field perspective, anyway thanks.

Best,

Kristian

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

scriptrunner

issue

jira-service-desk

jira-service-desk-server

reporter