When we review features with stakeholders, we need to consider and refine both the description (user problem) and the acceptance criteria (definition of done) before it can be approved.
We also need the acceptance criteria to sync to an equivalent field in AzureDevOps.
The custom layout editor, updated in September 2020, appears to have removed the ability to display the acceptance criteria below the description field.
We need the Acceptance Criteria to be a primary—not auxiliary—part of a feature / user story. We need to reinforce this importance by displaying it in the main content area.
We review both the description and acceptance criteria with stakeholders before considering a requirement “approved”. And, our QA engineers and stakeholders use the criteria to test the features after coding. We want anyone writing a feature / user story to know they need to think about this.
We could display the acceptance criteria inside the description field, but we're mapping acceptance criteria to its own field in Azure DevOps, so this doesn't work.
Note: We'll need the same ability for epics. Anything that can be completed, needs a place to display the 'definition of done’ (acceptance criteria).
Acceptance Criteria custom field displays in the main content window, prefereably just below the Description
Acceptance Criteria field syncs with Azure DevOps (we believe this already works)
Nice to have: Show both the description and acceptance criteria in one full-screen view.
Really surprised as a product tool that acceptance criteria is not a standard field or even an option to turn on or off as required. No brainer tbh!