add note to README about assigning labels for new issues#409
add note to README about assigning labels for new issues#409
Conversation
mrabbitt
left a comment
mrabbitt
left a comment
There was a problem hiding this comment.
Looks fine to me, though perhaps it could use some more explanation regarding feature requests (see my other comment).
Also, will these instructions need to be updated again if we introduce issue templates which automatically add the labels (as per one of the line items in #368)?
This should probably be reviewed by someone else who's been around longer than me and is familiar with the way the team works.
|
|
||
| ## Filing a new issue | ||
|
|
||
| If you run into an issue or would like to request a feature, please file an issue. |
There was a problem hiding this comment.
For an issue that requests a new feature, it may require both UX design work and engineering work. What label(s) are appropriate in that situation?
There was a problem hiding this comment.
it sounds like we may no longer need these labels. if so, we could get rid of them and the prefixes (at least moving forward)
@tam-janice, given the new board structure, will we no longer have separate eng and dev tickets? asking b/c traditionally the tickets were either prefixed with [ENG] or [UX] (or alternatively assigned similar labels).
There was a problem hiding this comment.
we could also repurpose the labels for "engineering"-only (tech stuff, chores) and "UX"-only tickets (design that isn't meant to be handed off to dev), which would distinguish them from a story/task that goes through the whole lifecycle.
There was a problem hiding this comment.
Here's what I'm thinking:
- We remove the prefixes [eng] and [UX]
- We will keep the column 'in design'
- If something needs design, it'll jsut be assigned to me and I'll take care of it
- there will never be a ticket that reqires both UX and eng. If it's an eng ticket design should already be done
Does this work?
3 participants
Addresses #368