RELATED IDEAS
Create a separate record for acceptance criteria
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.
User Story
As a <Type of user>
I need to <do something>
for <some reason>
which <gives me some benefit OPTIONAL>
Acceptance Criteria
Scenario: <describe the use case>
Given: <I have met some criteria>
When: <I perform an action>
Then: <I achieve my expected result>
-
ADMIN RESPONSEMay 30, 2018
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.
© 2024 Aha! Labs Inc.•All rights reserved
By separating out the Acceptance Test Criteria into a unique record type rather than using custom sub-tasks, we can continue to leverage the ability to show progress of the sub-tasks within the Gantt capability. Developers and product owners , et al, can be maintain their visual progress (Gantt charts) and Quality team members will still have clear identification of their activities.