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

How to set default value for custom field only on Create screen?

I'm trying to use Behaviours plugin to set default value for some custom fields when create issue. 

I created Behaviour and added script

import com.atlassian.jira.component.ComponentAccessor
def tasksFld = getFieldByName("Tasks")
def customFieldManager = ComponentAccessor.getCustomFieldManager()
def customField = customFieldManager.getCustomFieldObject(tasksFld.getFieldId())
def defaultValue = """[Tasks|https://]""".replaceAll(/ /, '')

if (getFieldScreen().name == "RM CreateScreen 2.0") {
tasksFld.setFormValue(defaultValue)
}

 but I did not get needed result - seems like condition 

getFieldScreen().name == "RM CreateScreen 2.0"

never works. It does not put value to field when issue created and screen "RM CreateScreen 2.0" is used.
Am I doing something wrong?
Maybe there is another method to restrict behaviours only for create issue operation? Or don’t overwrite the custom field if it already exists?

2 answers

1 accepted

0 votes
Answer accepted

resolved with 

if (getAction()?.id != 1) {
return // not the initial action, so don't set default values
}
1 vote

Hello, 

I guess the problem is with getFieldScreen().name == "RM CreateScreen 2.0". Are you sure that your create screen is called "RM CreateScreen 2.0"? You can verify it by logging the name of the screen in the behavour. For example you could add to the beginning of your behavour log.error("getFieldScreen().name") and have a look in atlassian-jira.log what the name of the screen is.

But do not do it. Better use another function which is getActionName(). This function always returns the transition name. In your case it will be "Create Issue". Try to replace your code with this one:

if (getActionName() == "Create Issue") {

tasksFld.setFormValue(defaultValue)

}

It must work. 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

174 views 2 1
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