Taiga-front: Stories should support validation/acceptance criteria

Created on 9 Jul 2015 · 6Comments · Source: taigaio/taiga-front

Scrum related: User stories are often broken down into:

Story, Acceptance Criteria, Tasks, and Impediments.

There is currently no way in Taiga to track acceptance criteria outside of tasks, or typing them into the story description itself.

Acceptance criteria should have their own set of permissions, typically owned by stakeholders.

Acceptance criteria should have two states: "Accepted" "Not-accepted"

Once a story's validation criteria are accepted, it can be moved from "awaiting test/validation" to "done" - though this should not be be enforced programmatically.

taiga-6-clean-up

Source

lincolnthree

👍11

Most helpful comment

:+1:
User stories without acceptance criteria != scrum
Also I would argue that != kanban

Without ACs it's just a wishlist. We need ACs to provide the definition of done.

lonix1 on 7 Aug 2019

👍2

All 6 comments

Agree with this 100%

ktallon on 10 Aug 2017

👍1

Hello,
Is there any plan for this feature, Taiga team?

lanphan on 14 May 2018

👍1

Would like to see this feature being added as well. Even though it's been 4 years since this issue was added.

nathanprins on 6 Feb 2019

👍2

:+1:
User stories without acceptance criteria != scrum
Also I would argue that != kanban

Without ACs it's just a wishlist. We need ACs to provide the definition of done.

lonix1 on 7 Aug 2019

👍2

We have been doing some housecleaning work prior to Taiga6 upcoming release and we are rejecting old issues that we didn't correctly attend back then. Since Taiga6 brings a significant UX/UI rework, we encourage you to wait and see if Taiga6 satisfies this need and open a new issue if that's not the case. This time we will make sure to review it when it comes through. Thank you very much on behalf of the Taiga Team!