RELATED IDEAS
Merged idea
This idea has been merged into another idea.
To comment or vote on this idea, please visit APP-I-576 Option to make custom fields mandatory / required.
Make custom field required.
Merged
At the Feature level, I would like the ability to make some fields required... so when working in the feature board or adding a new feature card, I would like certain Custom (and some standard) fields required
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +2
© 2024 Aha! Labs Inc.•All rights reserved
We use a number of custom fields and need our Product Managers to fill them out for proper reporting. Making them required would reduce our need to follow-up and the delay that causes.
Having specific fields required to be filled in for a new feature or, particularly, before that feature can be set a specific status would be very helpful. I am trying to trigger workflow (both within and external to the system) based on feature status and some of those workflows will require specific information to be passed to them.
We need this feature to flag features to a field called "requires documentation". When set it allows us to sent this field to Jira and our training department uses it to create documentation for new features
It would be great to have this capability available as an option for any field in Features, Releases, Initiatives etc. Give me, the user, the ability to customize Aha! to be at its best for my operational needs.