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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,559,636
Community Members
 
Community Events
185
Community Groups

Behaviours - differentiate between creation and editing of an issue

Hello,

 

I would like a section of my Behaviours script to apply only to newly created issues, and not to issues being edited. How can I specify this?

 

Thanks in advance!

1 answer

1 accepted

1 vote
Answer accepted
Jenna Davis
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Dec 18, 2017

Hello, 

You can use 'getActionName()' to tell what action you are currently in. For the 'Create' action, you would do something like this:

getActionName() == "Create"

For example, here's a simple behaviour that will set the description to 'Hello' on create. 

def field = getFieldById("description")
if(getActionName() == "Create"){
field.setFormValue("Hello")
}

Hope this helps! Let me know if you have any other questions. 

Jenna 

Hi Jenna,

Thanks, that's very useful to know.

 

For my particular solution I ended up doing this, in order to check whether the field in the edit view was different from the value stored in the database:

 

//grab due date in edit view
def dueDate = getFieldById(getFieldChanged());

//grab current due date from database
CustomField currentDueDate = customFieldManager.getCustomFieldObject('customfield_10025');
String currentDueDateAsString = (underlyingIssue?.getCustomFieldValue(currentDueDate) as Date)?.dateString;

//check if date was changed in edit view
if(!dueDate?.value || (dueDate?.value as Date)?.dateString != currentDueDateAsString) {
    
    //require reason box so that user is forced to enter text
    reasonBox.setRequired(true);
}

As this differentiation turned out to be more relevant than whether the issue was newly created or not.

 

But I find this information very useful, so thanks again.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events