From ed22782d427b07762b1b5ce61f1f09cf54e16a5a Mon Sep 17 00:00:00 2001 From: Jack Wang Date: Thu, 9 Jan 2025 01:42:48 -0500 Subject: [PATCH] Update platform-user-story.md (#16862) --- .github/ISSUE_TEMPLATE/platform-user-story.md | 24 ++++++++----------- 1 file changed, 10 insertions(+), 14 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/platform-user-story.md b/.github/ISSUE_TEMPLATE/platform-user-story.md index 366e238606a..6ec57ed53dc 100644 --- a/.github/ISSUE_TEMPLATE/platform-user-story.md +++ b/.github/ISSUE_TEMPLATE/platform-user-story.md @@ -21,21 +21,21 @@ so that _[Outcome - what is the value add to the user]_." ### Description/Use Case ### Risks/Impacts/Considerations ### Dev Notes ### Acceptance Criteria @@ -43,12 +43,8 @@ _Use this section to describe any useful technical information to duplicate an i What is Acceptance Criteria? A set of conditions or business rules, as defined by the Product Owner, which the functionality or feature should satisfy, in order to be accepted by the Product Owner. -Use the following template when creating new Acceptance Criteria: +Write the acceptance criteria as a list that can be checked off as work progresses. For example: -"Given _[describe the precondition]_, when I _[describe the action performed]_, then I expect _[describe the expected outcome]_." - -_OR... it may be written as a bulleted list._ - -- _Time must be displayed as HH:MM:SS_ -- _Delivery rate must be shown as a percentage_ +- [ ] _[Time must be displayed as HH:MM:SS]_ +- [ ] _[Delivery rate must be shown as a percentage]_ -->