Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

testing "issue" creation #63

Open
SusanBrown opened this issue Mar 11, 2013 · 2 comments
Open

testing "issue" creation #63

SusanBrown opened this issue Mar 11, 2013 · 2 comments

Comments

@SusanBrown
Copy link

Testing to see If I can create an "issue" (a misuse of the word that I loathe).

@SusanBrown
Copy link
Author

I don't see how to prioritize or reorder items in this list of issues. Zen mode seems nice.

Ah I see that the keyboard shortcuts allow for adding labels, moving up and down, etc. so that is better. And apparently images can be dragged in.
semicolon

@jchartrand
Copy link
Owner

You can't explicitly prioritize in GitHub. I'd imagined we'd prioritize and group bugs (by iteration or whatever) in a document that sits apart from GitHub.

But, GitHub does allow 'grouping' bugs in three ways: 'assignment' (to a person), 'milestone' (which would probably map to our iterations), and 'label'. The label is where you can assign an informal (informal in that the labels aren't a controlled - within GitHub - vocabulary) priority, but apparently there's no easy way to order on the labels. Here's a post that describes how some people use labels to manage/organize bugs, including descriptions of the label names they use:

http://programmers.stackexchange.com/questions/129714/how-to-manage-github-issues-for-priority-etc

This set of labels (taken from different parts of that document) might work:

Category Labels (could also use all caps to visually separate)

type:Task
type:Bug
type:Feature
type:Discussion
Priority Label

priority:High
priority:Normal
priority:Low
Status Labels

status:confirmed
status:deferred
status:fix-committed
status:in-progress
status:incomplete
status:rejected
status:resolved
status:blocking
status:blocked (the blocking issue blocks the blocked issue)
The status labels would correspond to some of the steps in the process document on which Megan is working, e.g., if all bugs are entered in GitHub on Friday afternoon after the Friday morning iteration meeting (or at least assigned, if they'd already been entered, to the 'milestone' for the current iteration), then Andrew and I would go through them Monday morning and mark their status as in-progress or confirmed or blocking, etc. as we talk through them in more detail. We'd review and mark them all by Monday night. I know you asked Megan to create this process doc, but if you'd like me to help her with it, or possibly first draft something for her review, just let me know.

james

On 2013-03-10, at 8:18 PM, SusanBrown [email protected] wrote:

I don't see how to prioritize or reorder items in this list of issues. Zen mode seems nice.


Reply to this email directly or view it on GitHub.

issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants