Re: [galaxy-dev] What happened to 'normal' priority on the issue tracker?
I just casually read the bitbucket blog and it seems that "Normal" is gone until the ticket for custom issue priorities is solved: http://blog.bitbucket.org/2011/08/08/issue-tracker-updates https://bitbucket.org/site/master/issue/2930/custom-issue-priorities On 2011-08-09 18:57, Jennifer Jackson wrote: > Hi Peter, > > The most important part of a ticket is putting clear comments at the > very top that will help us when we triage, assign, and such. This is > what we use to adjust the category assignments. Before we triage, the > assignments are nice, but don't drive project priorities. > > So, it is OK leave almost everything as default. In particular, leave > the state as "new" and responsible as "unassigned" so that we can easily > locate new tickets. > > The form is controlled by the bitbucket team to a large degree, but I'll > check out the settings anyway to see if something more neutral can be > made the default. Major for everything new _is_ a bit alarming :) > > Thanks! > > Jen > Galaxy team > > On 8/9/11 2:50 AM, Peter Cock wrote: >> Hi all, >> >> I'm just filing a bug on bitbucket, and noticed the default priority >> is now major (!) >> >> We can choose: Trivial, Minor, Major, Critical, Blocker >> >> Wasn't there previously a 'Normal' which was the default? >> >> Peter >> ___ >> Please keep all replies on the list by using "reply all" >> in your mail client. To manage your subscriptions to this >> and other Galaxy lists, please use the interface at: >> >>http://lists.bx.psu.edu/ > ___ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
Re: [galaxy-dev] What happened to 'normal' priority on the issue tracker?
Hi Peter, The most important part of a ticket is putting clear comments at the very top that will help us when we triage, assign, and such. This is what we use to adjust the category assignments. Before we triage, the assignments are nice, but don't drive project priorities. So, it is OK leave almost everything as default. In particular, leave the state as "new" and responsible as "unassigned" so that we can easily locate new tickets. The form is controlled by the bitbucket team to a large degree, but I'll check out the settings anyway to see if something more neutral can be made the default. Major for everything new _is_ a bit alarming :) Thanks! Jen Galaxy team On 8/9/11 2:50 AM, Peter Cock wrote: Hi all, I'm just filing a bug on bitbucket, and noticed the default priority is now major (!) We can choose: Trivial, Minor, Major, Critical, Blocker Wasn't there previously a 'Normal' which was the default? Peter ___ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ -- Jennifer Jackson http://usegalaxy.org http://galaxyproject.org/Support ___ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
[galaxy-dev] What happened to 'normal' priority on the issue tracker?
Hi all, I'm just filing a bug on bitbucket, and noticed the default priority is now major (!) We can choose: Trivial, Minor, Major, Critical, Blocker Wasn't there previously a 'Normal' which was the default? Peter ___ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
