• Community
  • Products
  • Jira
  • Questions
  • The field "Original Estimate" is made as Mandatory using the Validator at the Create Issue Work Flow action - But even after the values are entered in that field it is still saying orginal estimate is required

The field "Original Estimate" is made as Mandatory using the Validator at the Create Issue Work Flow action - But even after the values are entered in that field it is still saying orginal estimate is required

The field Original Estimate is made as Mandatory using the Validator at the Create Issue Work Flow action - But even after the values are entered in that field it is still saying orginal estimate is required

4 answers

instead of making the original estimate as mandatory, We made the entire time tracking field as mandatory and wrote a post function to copy the original estimate into remaining estimate by default while creating the issue to avoid the above

Thanks for the response. My only concern with this is that we have a lot of active projects in the company and I'm concerned that changing a field to be required might affect other projects that use Time Tracking. I'll give that a go and see if I get any angry phone calls from my colleagues!

I had to create a separate field configuration for the specific issue types that require Time Tracking (as we have several issue types used on the same database), but it worked! I didn't need the post functions - as soon as I added Time Tracking as a required field then the Original Estimate field on my issue creation form was marked as required and seemed to process correctly once a value was entered for Original Estimate.

Thanks you both for your help. I'm not sure how to award you some extra Karma, but you deserve it!

You can accept saravanan's answer and that would give them karma. I converted my comment to an answer in case you want to accept it, but saravanan's gave more information (mine was just more of a follow-up on your comment). :)

Just make sure that the field configuration scheme you use is only associated with your project and you won't affect anyone else's. :)

I've run into this one too... Anyone got any ideas?

How do you reference original estimate in simple validation script to ensure it is required based on a specific issue type on create issue.   tried the following code:

if (issue.issueTypeObject.name == "Task"){
	breturn = true;
        if(cfValues['Original Estimate'] != null && !cfValues['Original Estimate'].equals("")){
		breturn = true;
	} else {
		breturn = false;
	}
        return breturn;
} else { 
	return true;
}

Using Jira 5.2 ---- Should the field be timetracking instead of Original Estimate?

yes - time tracking consists of original estimate , remaining estimate etc - i made the entire time tracking field as mandatory to avoid the issue

I am not able to make it a mandatory field due to other issue types not requiring it.

create a seperate work flow and field configuration scheme for the issue type that requires it

In your case you could still set "0m" as a value.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,914 views 12 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot