RELATED IDEAS
Indicate required fields when editing a record
We need the ability to make standard and custom fields mandatory for existing records.
When a record is being edited, the UI should flag empty required fields so that the user is prompted to update them. This will help us ensure that critical information is included for all of our records.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +2
1
MERGED
Mandatory fields for custom layouts
Be able to make certain fields on a feature mandatory for custom layouts after a record has been recorded. It does not need to be mandatory when the record is initially created but at a certain point later in its lifecycle, pre development.
0
Future consideration
100% agree with Sarah
This is absolutely critical functionality. Integration with other systems that have fields required at all times (not just on entry) means the record will not synchronize properly if that field is not valued in Aha. Why make it required only on entry, when it can be cleared in edit? Please make this configurable on ALL fields.
Being able to insist on required fields on existing records is critical for reporting and tracking etc. Please consider a configurable option for fields to be required when editing a record.
Sometimes it's difficult to understand how Aha designs their features and this one is a good one: you can setup mandatory fields at creation time but you can remove the same fields in edit mode... what the point?!?
Thank you to bring this feature.
Hard to believe we have to request and vote on such critical, table stakes functionality. If Aha believes it would negatively impact the usability of the product, then make it an optional, admin-configurable feature that can be enabled or disabled globally, so those of us who need it can turn it on for our organization without affecting those that don't.
This is especially important if you use a Jira integration with required fields on Jira's end. Every time a user sends a record to jira and the required fields are empty on Aha's side, they get an error and end up creating a support ticket to resolve the problem. We then have to explain to them that fields X, Y, and Z are required fields in Jira and we can't set them to required in Aha, so they'll have to remember it for next time.
This is required functionality to ensure an Idea/Initiative/feature is ready to move to next step in the process.
We have made a recent change related to Goals in that every feature must be mapped to a standard and newly redefined set of goals. Due to this change we've added the Goals field to the Create Feature form and set it to be 'required' which addresses this need for new features, but the multitude of existing features are missing this mapping, so it would be a huge benefit to be able set this standard field as mandatory so that upon the next edit, users are forced to map the existing feature the appropriate goal.
This is really important for us and should be implemented ASAP.
Agree this is the type of feature that would be very valuable for capturing the required fields.
Rally supports marking a field as Required for existing records. If a user edits an existing Record, Rally will inform the user they must fill in all Required fields in order to save their changes. We have found this useful for getting users to add needed data to records that are still under active development.
This description is the use case that is important to us.