Zephyr Scale Cloud Ideas

I had to create a custom field called "FolderLoc" JUST so I could make it required. The only reason I had to do this is because I can't set "Folder" to be a required field.

This is a hack that creates confusion and maintenance issues down the road and it wouldn't be necessary if only I could mark the "Folder" field as required.

Clearly useful function to avoid quality drift on content

Per discussion with Assis regarding support ticket TMJCSUP-5073 (item #2 that I mentioned), he said I should take a look at this idea. To me since every business has different fields they deem are mandatory, it would seem to be best if on the 'Configuration' screen all default fields have a parameter to indicate whether the value is required or not for each record being added/updated -- regardless of whether a user is adding an individual test case, or using bulk edit, import from file, API or other methods. Obviously, there are some "key" fields that are system generated or "must haves" that should always be required.

My organisation really needs this to enforce our documented standards.

We want to make the following fields mandatory:

• Objective

• Estimated Time

• Component

• Folder

yes, we are also waiting for this feature. would be very helpful to et a default value which is directly taken over when a new test case is created

This is absolutely necessary.

As an admin, I need the ability to set ANY field on the Details tab as required in order to enforce our process. We are getting a lot of test cases without a folder value or estimated time, etc.