Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

ScriptRunner Behaviours: cannot pre-fill field Email in Support Contact Form


With same code I can set a field Description, but cannot set a field Email. See the code below. The result: the content of field Description is filled with email address, but field Email stays empty. The name of field Email is correct. Why the behavior is different? How I can set a content of field Email?

import com.atlassian.jira.component.ComponentAccessor
import com.onresolve.jira.groovy.user.FieldBehaviours
import groovy.transform.BaseScript
@BaseScript FieldBehaviours fieldBehaviours

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


1 answer

1 accepted

Another function: getFieldByName("Email") gives a result, so I have a solution. Why getFieldById("email") doesn't function, is still unclear.

Deleted user Aug 12, 2019

Hi Alex

getFieldById only works with default fields (such as description, summary, etc.) or in the form of getFieldById("customfield_XXX") where the XXX is the actual ID of the custom field.

When you are configuring a custom field, you can find its ID by looking in the URL. There will be a number there. Replacing XXX with the number should fix your issue.

Why this works like this is because you can have 2 custom fields with the same name, so the custom field name isn't actually a good fit as an ID as you'd expect an ID to be unique.

Kind regards

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events