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,462,033
Community Members
 
Community Events
176
Community Groups

Make original estimate required on sub-tasks

Edited

Hello

I create a behaviour associated with the "Original Estimate" field. I mark the field as being "Required" and this works, I see a little red asterix beside the field on the sub-task creation form.

However, the following script does not work and when I leave the field empty, I can still create the sub-task, no error at all.

def originalEstimateField = getFieldById("timetracking_originalestimate")
def originalEstimateValue = originalEstimateField.getValue() as long

if (originalEstimateValue != null){
originalEstimateField.clearError()
}else{
originalEstimateField.setError("All sub-task require an original estimate.")
originalEstimateField.setFormValue(null)
}

I also tried this instead for the condition:

if (originalEstimateValue > 0){

 Please help!

1 answer

0 votes

Hi @Guy LaRochelle 

What are you trying to achieve here? I'm a bit confused about the error message you wrote.

Are you trying to make original estimate field for a subtask mandatory? If yes, when? During creation? Through out the subtask's lifecycle? Only during a specific transition?

Why does the error message states something about "all subtasks"? 

Suggest an answer

Log in or Sign up to answer