Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

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

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()
getFieldById("description").setFormValue(currentUser.emailAddress)
getFieldById("email").setFormValue(currentUser.emailAddress)
 

 

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
Jorden

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

35 views 0 2
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