It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Create Issue in project depending on custom field (ScriptRunner)

Hey there,

I want to create a scripted post function which creates issues in project X. Project is depending on a custom field "customer" on the transition - screen.

Has anyone experience with this and / or could help me with this?

This is the code a colleague hand me over but it doesn't work right:

import com.atlassian.jira.ComponentManager
import com.atlassian.jira.issue.CustomFieldManager
import com.atlassian.jira.ComponentManager
import com.atlassian.jira.util.ImportUtils
import com.opensymphony.workflow.WorkflowContext
import org.apache.log4j.Category

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.user.util.UserManager
import com.atlassian.jira.user.ApplicationUser
import com.atlassian.crowd.embedded.api.CrowdService
import com.atlassian.crowd.embedded.api.User
import com.atlassian.jira.issue.MutableIssue
import com.atlassian.jira.issue.IssueManager
import com.atlassian.jira.bc.issue.IssueService;
import com.atlassian.jira.issue.IssueInputParameters

log = Category.getInstance("com.onresolve.jira.groovy.DelegateIssue")
log.error("Processing: " + issue.key);

CustomFieldManager customFieldManager = ComponentManager.getInstance().getCustomFieldManager();
IssueManager issueManager = ComponentAccessor.getIssueManager();
IssueService issueService = ComponentAccessor.getIssueService();

Object readLocalCustomField(issue, String fieldName) { // Read by NAME
	CustomFieldManager customFieldManager = ComponentManager.getInstance().getCustomFieldManager();
	def cf = customFieldManager.getCustomFieldObjects(issue).find { == fieldName}
	return cf.getValue(issue)  //return issue.getCustomFieldValue(cf)

def project = readLocalCustomField(issue, "customer")
log.error("Customer: " + project);

issueMgr = ComponentManager.getInstance().getIssueManager()
projectMgr = ComponentManager.getInstance().getProjectManager()
String currentUserName = ((WorkflowContext) transientVars.get("context")).getCaller();
UserManager userManager = ComponentAccessor.getUserManager();
ApplicationUser currentApplicationUserObj = userManager.getUserByName(currentUserName);
User currentUserObj = currentApplicationUserObj.getDirectoryUser();

//User currentUserObj = CrowdService.getUser(currentUserName);
def wasIndexing = ImportUtils.indexIssues
ImportUtils.indexIssues = true

IssueInputParameters issueInputParameters = issueService.newIssueInputParameters();

// Regular Fields
// Custom Fields
def customField = customFieldManager.getCustomFieldObjects(issue).find { == "foo"};
issueInputParameters.addCustomFieldValue(customField.getIdAsLong(), "bar");

IssueService.CreateValidationResult result = issueService.validateCreate(currentUserObj, issueInputParameters);
if(!result.isValid()) {
    log.error("could not create issue: " +  result.getErrorCollection());

newissue = issueService.create(currentUserObj, result).getIssue()

// get the current list of outwards Blocks on links to get the sequence number
linkMgr = ComponentManager.getInstance().getIssueLinkManager()
def sequence = 0
for (IssueLink link in linkMgr.getInwardLinks( {
    if ("Blocks" == {
linkMgr = ComponentManager.getInstance().getIssueLinkManager()
// TODO: Should check that 10000 is always the link id for Blocks
linkMgr.createIssueLink (,, 10000, sequence, currentUserObj)
ImportUtils.indexIssues = wasIndexing


Any idea?  
I'm grateful for any hint.


2 answers

1 accepted

1 vote
Answer accepted

I can't help with the scripting problem, but, I can suggest a non-programming alternative:

Use the Create Issue post function from Create on Transition for JIRA. Then use %original_customer% substitution variable in the project field.

Thanks! I thought I can just set a fix value in the project field when Create issues with the post function. Makes much more sense than a script with less scripting knowledge :D

Then I just have a short question what exactly I have to fill in the Issue Key field when setting up a Link? The only thing I can't get to work now. I appreciate your reply.

Are you trying to link the new issue to the original issue as a Blocks link? Then use *%original_key%* and *Blocks* for the fields. The pick the link direction you need.

Ignore the *s, I don't know why we don't have wiki markup support in the comment editor.

0 votes
JamieA Nov 25, 2014

Can you give us more info on how it's not working?

An easier alternative might be to use the built-in script, "Clone and link" with some "additional code" for setting the project. I think this has been done before.

Ìt's not working like it does nothing .. But got another solution so it's ok. Thank you anyway :)

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Next-gen

Introducing subtasks for breaking down work in next-gen projects

Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...

1,020 views 13 15
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you