[2pt] As a Thoth Service owner I want to have a list of criteria that constitute an issue so that I can measure when an issue is has enough information

open-services-group / community

This repository handles a few common things, it is mainly used by our bots...

GNU General Public License v3.0

8 stars 24 forks source link

[2pt] As a Thoth Service owner I want to have a list of criteria that constitute an issue so that I can measure when an issue is has enough information #143

Closed Gkrumbach07 closed 2 years ago

Gkrumbach07 commented 2 years ago

Persona / User

Thoth Guidance Service owner

User's Story

I want to have a list of criteria that constitutes an issue

Reason

so that I can measure when an issue is has enough information

Define Done

[ ] A PR updating Thoth T&C with a new issue quality section

Additional Info

Current terms and conditions

Gkrumbach07 commented 2 years ago

Currently all Thoth issues must have these to be considered refined

have a User Story
list of high-level Acceptance Criteria/Goals (that is signed off by the team, and unchangeable)
categorization if it is a [spike]
checklist of detailed Acceptance Criteria (that might extend over the lifetime of the card)
(optional) a measure of complexity (story points)/time estimate
list of References
might have a due date assigned and confirmed by the team lead

suppathak commented 2 years ago

Do you think it would be a better idea if we could create different labels of issues. Considering, not all issues have user story or any other criteria listed above. May be creating labels for different issue type would be better. wdyt?

Gkrumbach07 commented 2 years ago

Currently Thoth uses these labels to describe an issue:

kind/bug - Categorizes issue or PR as related to a bug.
kind/cleanup - Categorizes issue or PR as related to cleaning up code, process, or technical debt.
kind/demo - This is an Issue or PR someone want to give a demo or request a demo.
kind/deprecation - Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
kind/documentation - Categorizes issue or PR as related to documentation.
kind/feature - Categorizes issue or PR as related to a new feature.
kind/question - Categorizes issue or PR as a support question

I was thinking that each support question could be categorized into feature, question, or bug

questions might not have user stories... but I think we can force questions into a user story format if we have to.

suppathak commented 2 years ago

Yup, It does makes sense.

Also, It seemed to me that this particular issue is similar to #145 . Wdyt? Are there any difference between the two?

Gkrumbach07 commented 2 years ago

I would argue that issue #145 comes after this issue. This issues deliverables is just criteria for what makes an issue, where as #145 is about creating/altering specific templates.

Gkrumbach07 commented 2 years ago

/assign @Gkrumbach07 /assign @suppathak

Gkrumbach07 commented 2 years ago

Changed acceptance criteria to accept Pep's PR as a definition of done.

/assign @codificat /unassign @suppathak /unassign @Gkrumbach07