Require fields by status

I am creating a workaround in order to "grade" features and epics based on if they have the things that we require as features and epics move through workflow. It would be so much easier for product managers to know at the time of updating and working a feature or epic that they can't update the status until they have completed the required fields.

seconding this, we desperately need the ability to require fields be filled out post- initial submission. At submission, we don't have all the info. But as we move through the workflow, we need to require fields be populated

We have fields that become required at specific statuses at all levels (Releases, Epics, Features). Because I cannot make them conditionally required when these statuses are reached I have to spend time on a weekly basis reviewing reports for records that are out of compliance. This is a complete waste of time when it could be automated as it is in most other applications that we use. I was disappointed to hear that this functionality is not currently in sight on your roadmaps as it is a much needed feature for our organization.

Agree with all below comments this is a must. Many users don't pay attention to integration failures. This causes Aha and ADO for us to be out of sync. Adding a comment through automation could be useful here but unfortunately you can't @ mention anyone in the comment. Sending another email also isn't great since it is an email and you can't send it to the user who flipped the status, only creator or assigned user options are allowed. Please address ASAP!

This would be very helpful in ensuring our data quality in Aha! and the reliance on the data. Thank you.

We make some fields required because the corresponding field in an integrated system is required. Allowing users to clear the field value then stops the sync, so the records are now out of sync. Our end users find this SUPER frustrating.

Its definitely missing logic here

Its required during create but it can be removed later, whats the point of being it required? there's no logic to make a field required all time.

There are some cases, where we don't need to fill in a field at create but required later when it enters a certain state.

Having it only at create forcing users to fill in some random value to create a feature just to bipass it.

I need condional fields to make ideas sorting more comfortable. Instead of having 10 fields at once, I want to have initial choise of 3 items (Marketing, Product, Process complains). For example, if you select Marketing, appears a choice of

- Activation

- Subscription

- Update

- etc

If Product issue is chosen, then showen choice of

- Freezing

- Rendering

- etc

Yes please - I need certain fields to have a value before moving to a new state. For example, making sure a Feature is assigned a Release before moving to a "Ready for Development" state.

Mandatory fields on Jira must be inherited through the integration to Aha to allow proper issue type handling ( e.g. prior to closure of an EPIC, our Jira mandate to set resolution field first ) – otherwise, it’ll create constant sync issues

To me, this seems to be like a bug or lack of basic functionality on aha

Definitely a need - especially when you do have integrations that become not useful as most users don't pay attention to any sync failure - admins have to monitor through the issues and it's not worth the time and effort when you are using in large implementation.

This is great! I would also ask that if we FLAG a story as BLOCKED (Similar to JIRA) that the system requires you to populate a Blocked Reason

Dates and estimates are fields that come to mind specifically.