This would be particularly helpful when trying to drive behaviours in larger organisations with multiple product managers.
I agree 100% with Howard's comment. This is a massive gap for product management organizations trying to gather feedback as it stops us from making sure we gather the necessary data to make good decisions when deciding what feedback to implement.
Is there any update on when this might be implemented? This is something that is currently driving me crazy with our users entering data. Not having required fields makes data entry the wild wild west!
I really need this feature. E.g. I've added a custom field called "Rationale" to Features and I need to make it impossible for anyone to create a new Feature without entering something in the Rationale field. I need to do the same for Ideas.
+1 on wanting to know when this is planned. it's a huge gap.
Any updates on when this will be implemented? We love the flexibility of Aha and rely heavily on meta data driven reports. For example, we list names of customers when adding user stories. Making the user name field mandatory would ensure the roadmap reports are always accurate.
Its extermely important to have this feature to make sure we data filled in by users
+100. Very important feature.
Already there for ideas, but missing for the other groups.
+1, Really need this feature.
+1 --- Wanting to do this now
This feature is very much required, as adding a custom field and not making it mandatory means no one will bother to update the fields.
We really need this field within Aha, as this would help tackle the issue of Data Integrity!!! At the moment because fields are not mandatory we have individuals who are not filling in certain fields that are a business requirement and due to this we have a high level of data missing. 90% of our time is chasing on missing data!!!
Definitely needed! Go one step further...be able to designate a field as mandatory/required based on another field. For example, when feature status changes from A to B, then make the Priority field required. Also don't limit this to custom fields.
Compulsory fields should be a standard function, it forces users to populate areas which are important to a business function, a lack of data from badly populated or unpopulated fields makes it more difficult for teams to plan ahead. Gathering important data from such fields is crucial nowadays.
I cant understand why this has not been developed sooner. This will be required by at least 90% of the Aha user base. Would love some feedback on a possible due date.
Not being able to enforce required fields is adding great complexity to our Jira integration... while introducing the need for heavier process control and data quality checking after the fact. Please support required fields to let your customers decide when they are appropriate to use. As this idea is over three years old, it would be great to get a sense if this is on the roadmap for 2018. Thanks
Seems like a basic and common functionality. Would really be helpful, especially with large groups.
I need this also!
for integrations with JIRA, often send to jira can fail because a custom field may be mandatory in jira, but not in aha, so people may try sending to jira without Aha being able to first ensure that mandatory fields are completed
Gimme Gimme Gimme
Very much needed. We use custom fields quite heavily and need to ensure certain key custom fields are populated.
We are really keen for this to be implemented - any update on timescales? there is a request for an update back in 2014 so it seems to have been around a long time?
You won't be notified about changes to this idea.