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

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

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
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...

226 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