Re: Changing trac defaults

2016-06-03 Thread Jean-Marc Lasgouttes
Le 03/06/16 à 22:30, Scott Kostyshak a écrit : I have set it to "unspecified". Is it better? Yes, in my opinion this is better. I also tried to make the ticket keyword plugin work again, but the only thing I managed to obtain is a link to our wiki page about keywords. I do not know how to d

Re: Changing trac defaults

2016-06-03 Thread Scott Kostyshak
On Fri, Jun 03, 2016 at 02:07:35PM +0200, Jean-Marc Lasgouttes wrote: > Le 02/06/2016 à 06:56, Scott Kostyshak a écrit : > > Now the default milestone is blank, which is great. Can we also have the > > version be blank by default? I think this would help, as discussed > > before, so that we know if

Re: Changing trac defaults

2016-06-03 Thread Jean-Marc Lasgouttes
Le 02/06/2016 à 06:56, Scott Kostyshak a écrit : Now the default milestone is blank, which is great. Can we also have the version be blank by default? I think this would help, as discussed before, so that we know if there is a version specified the user likely has that version. Currently the defa

Re: Changing trac defaults

2016-06-01 Thread Scott Kostyshak
On Sat, Mar 21, 2015 at 06:27:17PM -0400, Richard Heck wrote: > On 03/21/2015 05:59 PM, Scott Kostyshak wrote: > > On Mon, Mar 16, 2015 at 9:02 PM, Richard Heck wrote: > > > On 03/16/2015 07:43 PM, Scott Kostyshak wrote: > > > > 2. version. Currently it defaults to 2.1.3. I propose to have it > >

Re: Changing trac defaults

2015-03-21 Thread Scott Kostyshak
On Sat, Mar 21, 2015 at 6:27 PM, Richard Heck wrote: > On 03/21/2015 05:59 PM, Scott Kostyshak wrote: > Not an option, either, in the Admin panel that allows one to set such > things. Only the milestones we've created are choices. Ah, I see. Would creating an "unspecified" milestone be an option

Re: Changing trac defaults

2015-03-21 Thread Richard Heck
On 03/21/2015 05:59 PM, Scott Kostyshak wrote: On Mon, Mar 16, 2015 at 9:02 PM, Richard Heck wrote: On 03/16/2015 07:43 PM, Scott Kostyshak wrote: 2. version. Currently it defaults to 2.1.3. I propose to have it default to blank. - I prefer to have the user choose the version. Otherwise they m

Re: Changing trac defaults

2015-03-21 Thread Scott Kostyshak
On Mon, Mar 16, 2015 at 9:02 PM, Richard Heck wrote: > On 03/16/2015 07:43 PM, Scott Kostyshak wrote: >> 2. version. Currently it defaults to 2.1.3. I propose to have it >> default to blank. >> - I prefer to have the user choose the version. Otherwise they might >> just have skipped choosing it o

Re: Changing trac defaults

2015-03-16 Thread Richard Heck
On 03/16/2015 07:43 PM, Scott Kostyshak wrote: I am curious what others think of two changes to defaults for reporting a new bug: 1. milestone. Currently it defaults to 2.1.4. I propose to have it default to blank. - Georg proposed a way of dealing with milestones a couple of months (?) ago that

Changing trac defaults

2015-03-16 Thread Scott Kostyshak
I am curious what others think of two changes to defaults for reporting a new bug: 1. milestone. Currently it defaults to 2.1.4. I propose to have it default to blank. - Georg proposed a way of dealing with milestones a couple of months (?) ago that made sense. Part of what I remember is: don't as