An error occurred while fetching the assigned milestone of the selected merge_request.
Add customer label explanation
Merge request reports
Activity
Added 1 commit:
- 856dab89 - Update workflow items to match labels.
36 36 37 37 Workflow labels are purposely not very detailed since that would be hard to keep updated as you would need to re-evaluate them after every comment. We optionally use functional labels on demand when want to group related issues to get an overview (for example all issues related to RVM, to tackle them in one go) and to add details to the issue. 38 38 39 *Awaiting feedback*: Feedback pending from the reporter 40 *Awaiting confirmation of fix*: The issue should already be solved in **master** (generally you can avoid this workflow item and just close the issue right away) 41 *Attached MR*: There is a MR attached and the discussion should happen there 39 ~"Awaiting Feedback" Feedback pending from the reporter 40 *Awaiting confirmation of fix* The issue should already be solved in **master** (generally you can avoid this workflow item and just close the issue right away) 41 *Attached MR*: There is a MR attached and the discussion should happen there 37 37 Workflow labels are purposely not very detailed since that would be hard to keep updated as you would need to re-evaluate them after every comment. We optionally use functional labels on demand when want to group related issues to get an overview (for example all issues related to RVM, to tackle them in one go) and to add details to the issue. 38 38 39 *Awaiting feedback*: Feedback pending from the reporter 40 *Awaiting confirmation of fix*: The issue should already be solved in **master** (generally you can avoid this workflow item and just close the issue right away) 41 *Attached MR*: There is a MR attached and the discussion should happen there 39 ~"Awaiting Feedback" Feedback pending from the reporter 40 *Awaiting confirmation of fix* The issue should already be solved in **master** (generally you can avoid this workflow item and just close the issue right away) 41 *Attached MR*: There is a MR attached and the discussion should happen there 42 42 - We need to let issues stay in sync with the MR's. We can do this with a "Closing #XXXX" or "Fixes #XXXX" comment in the MR. We can't close the issue when there is a merge request because sometimes a MR is not good and we just close the MR, then the issue must stay. 43 43 *Developer*: needs help from a developer 44 *UX* needs needs help from a UX designer 45 *Frontend* needs help from a Front-end engineer 46 *Graphics* needs help from a Graphics designer 47 *up-for-grabs* is an issue suitable for first-time contributors, of reasonable difficulty and size. Not exclusive with other labels. 48 *feature proposal* is a proposal for a new feature for GitLab. People are encouraged to vote 44 ~UX needs needs help from a UX designer I'm wondering –since labels can have a description– if maybe we could simply link to the labels page (after adding missing descriptions to labels), or at least add a link to it. /cc @DouweM
36 36 37 37 Workflow labels are purposely not very detailed since that would be hard to keep updated as you would need to re-evaluate them after every comment. We optionally use functional labels on demand when want to group related issues to get an overview (for example all issues related to RVM, to tackle them in one go) and to add details to the issue. 38 38 39 *Awaiting feedback*: Feedback pending from the reporter 40 *Awaiting confirmation of fix*: The issue should already be solved in **master** (generally you can avoid this workflow item and just close the issue right away) 41 *Attached MR*: There is a MR attached and the discussion should happen there 39 ~"Awaiting Feedback" Feedback pending from the reporter 40 *Awaiting confirmation of fix* The issue should already be solved in **master** (generally you can avoid this workflow item and just close the issue right away) 36 36 37 37 Workflow labels are purposely not very detailed since that would be hard to keep updated as you would need to re-evaluate them after every comment. We optionally use functional labels on demand when want to group related issues to get an overview (for example all issues related to RVM, to tackle them in one go) and to add details to the issue. 38 38 39 *Awaiting feedback*: Feedback pending from the reporter 40 *Awaiting confirmation of fix*: The issue should already be solved in **master** (generally you can avoid this workflow item and just close the issue right away) 41 *Attached MR*: There is a MR attached and the discussion should happen there 39 ~"Awaiting Feedback" Feedback pending from the reporter 40 *Awaiting confirmation of fix* The issue should already be solved in **master** (generally you can avoid this workflow item and just close the issue right away) 41 *Attached MR*: There is a MR attached and the discussion should happen there 42 42 - We need to let issues stay in sync with the MR's. We can do this with a "Closing #XXXX" or "Fixes #XXXX" comment in the MR. We can't close the issue when there is a merge request because sometimes a MR is not good and we just close the MR, then the issue must stay. 43 43 *Developer*: needs help from a developer @dblessing @DouweM Regarding my previous comment, I've just added description for some labels in the labels page. :)
@dblessing Sorry for the spam, I see that the up-to-date MR is !2972 (merged), I'll close this one then! ;)
mentioned in merge request !2983 (merged)
Please register or sign in to reply