Allow setting limit as natural limit in spec limit column property

[jthi]

What inspired this wish list request? 

Dealing with "one-sided" specification limits which have second limit just for sanity check purposes and not being able to set it as natural/boundary limit in JMP.

What is the improvement you would like to see? 

Let set Spec Limit lower/upper limits as natural/boundary limits.

It is possible to have limits which cannot be exceeded (for example due to physical reasons) but they are still set (for example for sanity check reasons). In JMP if we are using Spec Limit column properties, this would mean that we have to delete such limits as JMP cannot set then as natural limit (they should be ignored in capability calculations and values beyond those handled as missing values). 

One suggestion how it could look like

Why is this idea important? 

Makes it easier to perform capability analysis as you wouldn't have to always remove the specification limit from column properties.

[mia_stephens]

Thanks @jthi , I found a related request and am adding the Jira.