I'm new to Aha, and contacted support to ask about recording acceptance criteria. There suggest was to use a template in the 'feature' for both he story & the AC, which to be fair does work. But in the same way we can link requirements to a feature, it would be great if AC was a separate 'form' in it's own right, like requirements, maybe with a tick to check off each requirement.
This is the simple template I use, and it works, just feels a bit forced.
As a <Type of user>
I need to <do something>
for <some reason>
which <gives me some benefit OPTIONAL>
Scenario: <describe the use case>
Given: <I have met some criteria>
When: <I perform an action>
Then: <I achieve my expected result>
|Release time frame|
Thank you for the request. The suggestions provided to you in terms of the templates are likely the best way to handle this use case. Another workaround would be to create a custom field called "Acceptance criteria" -- this would exist on every feature, and could be filled in as you need it.
At this time, we are not planning to add another specific record type around acceptance criteria but hope that one of the two workarounds can work for you.