You can now set required fields when adding new records — so you can bring consistency to how your teams enter data in Aha!
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?
this is critical for us, especially due to the integration with jira which fails because this
Is there an update on this idea?
Do we have any update on this?
This is a must feature Aha should have it ASAP.
We could definitely make use of this feature to achieve consistent data reporting with over 20 product managers.
Any approximate timescales for this? We desparately need it to help drive data quality and reduce the number of exception reports we need to manage.
I have the same Idea as shared with other commenters prevoiusly. I'm new(ish) to Aha but am REALLY surprised that with all this feedback over a significant period for something that seems to be assumed capability by many Aha users isn't in the Product.
@AHA PMs - given how much support there is for this feature and how long people have been asking for it, would be great if you could make this happen soon and if you could give us an ETA.
@AHA PMs - Thanks for hearing your users' feedback and the change in status to "Planning to implement". Could you please share a timeline - even which quarter would be helpful. Thanks.
Surprised this isn't already a feature of Aha! Please provide timeline as this is crucial to using Aha! at scale.
Thank you for your consistent feedback on this idea! We are actively developing this feature and plan to release it this quarter (next couple of months).
Absolutely necessary. Will prevent lots of synchronization errors with JIRA when you have mandatory fields. E.g. Country.
I agree with all that is said here. This is particularly important if, like us, you are planning to integrate with Jira. It would make dealing Jira mandatory fields much easier and less susceptible to error.
This is effectively a bug. Please fix ASAP.
It is very important issue for my team, implementation should happen ASAP.
This it not great if you have been using Aha for a while and created lots of custom fields that we still cant make mandatory.... :-( - really disappointed.
Our implementation is pretty sophisticated and established. We have a lot of existing custom fields and are unlikely to add (many) new custom fields. The key requirement for us wasto be able to make existing custom field mandatory - this is the problem we needed solving.
Thank you for the follow up comments. I believe both comments describe similar use cases, but I would like to confirm. Is the use case that you want to make custom and standard fields on existing records mandatory (i.e. features that have already been created)?
Yes, we need a way to make the existing custom fields mandatory on all feature records new and existing.
How soon can you deliver this?
We have existing custom layouts that use a mixture of standard fields and custom fields. We want to make some of the existing custom fields (which are already used on existing custom layouts) mandatory.
So far it looks as though we need to work around this by creating a new custom layout, re-add all our custom fields, apply mandatory and then request all Product Managers update their product configurations to use the new custom layouts. We have custom layouts for Products, Personas, Competitors, Initiatives, Releases, Master Features, and Features.
If I have misunderstood anything, please let me know.
I am echoing others people comments. I would have expected to be able to flag existing custom fields on a layout as required for existing record types (release, feature...). I see you can set a custom field as required when a new record type is created.
That is ok, but the real need is to have the user update the record with the required fields.
This is half implementation only, it's implemented only on create screen but later anyone can remove that mandatory field from feature. Ideally all mandatory fields should only have option to edit but not to remove.
Thank you for the follow up and clarification here.
This week’s release introduced required fields for record creation. As you move forward and collect key data, this allows you set required fields and to create more consistency to how your teams enter data in Aha! moving forward.
Some recent comments asked for the ability to make these fields required in the viewing and editing experience — particularly for existing records. This was not an area of focus for this release. While we see the benefit of capturing this data in this view, this would have a very negative impact on usability in the application.
That said, we would like to continue to monitor feedback in this area. We have created a new idea to track this request here: https://big.ideas.aha.io/ideas/A-I-7817. Please vote on that idea and comment with any specific use case (or user flow) that you’d like to be considered.
Hang on. So to confirm, fields are now mandatory (if you set them to be) on creation but on edit you can remove data and they not mandatory anymore? That’s ridiculous, that’s very non standard behaviour.
You won't be notified about changes to this idea.