RELATED IDEAS
Field default value
This is a basic function of any database and should be part of the core functionality. This should also extend to custom fields
1
MERGED
Enable Choice Lists to have a Default choice setting
We have added a custom field with the Predefined Choice List. In our use case the choices are: On-track, At Risk, Off-track, Completed. We would like to have the ability to default the field to "On-track" in the field settings. Or perhaps add anot...
0
Future consideration
1
MERGED
Assign Default Value on Custom Field
When adding a custom field to a layout, particularly a predefined choice list item, it would be helpful to optionally indicate one of the choices as a default, so that you can ensure that the value is at least populated with something useful rathe...
0
Future consideration
I have a similar use-case, I would like to set a table in custom fields that will be there when creating new requirements.
This is needed for saving the team's effort to choose each time the default value which in most cases is the value we should have there. It should be part of the configuration at the custom field layout.
Same here. I just like to have the option to select default values for each field - at least in Features. And I agree, that should be basic functionality, not Enterprise+.
From a configuration perspective I think the best place to define those field defaults would be in the "layout" definition screen, as that provides a good overview and direct access to "all" fields of a Feature.
This seems like pretty basic functionality. Why isn't this supported for all SKUs?
Forgot to mention...setting a default should not be an enterprise + feature. This isn't about workflows, this is basic and expected functionality expected.
This is surprising that it is a gap. When trying to gain adoption, drive whatever your best practice is, improve efficiencies, and mitigate errors, the option to set common defaults is both common and needed.
This would also be useful to my workflow. Ideally, I'd like to set a color-coded default value to, "none" in order to call attention to the field as needing to be populated with information.
Specifically I want to set all feature estimates to default to 1. This would allow us to measure capacity and do capacity planning in counts.