On 12 Okt., 16:01, kcrisman <kcris...@gmail.com> wrote: > I don't know how to change Trac's settings. But here are two things > that someone should change, that are hopefully (?) easy. > > 1) I've been a little annoyed that sometimes people set a ticket to > 'needs info', and then the only option is to set it to 'needs > review'. Can we get something that sets it back to 'new' as well, if > this happens to a 'new' ticket?
I couldn't [quickly] find a way to change that; the only way to set a ticket back to "new" seems to be to close and reopen it (which only the release manager should do). I'm pretty sure there's a way to change that in trac configuration files though. It's also annoying one cannot switch from "needs info" to "needs work" IIRC (and some other state changes as well, like from "needs work" to "positive review"). Slightly related: - We currently don't use the severity field at all (hence it isn't visible either), but just have / use "priority" instead, which is a slightly different thing. We for example also have "priority: trivial", whatever that's supposed to mean. A trivial change can well be of high importance (or severity), but it's not bad to indicate that it is a trivial change even if it's "critical" or a "blocker". - We have a *component* "memleak"; IMHO we should add "memory leak" and e.g. "performance regression" to the possible *types* a ticket can have (which are currently only "defect", "enhancement" and "task"). - We /may/ add "confirmed" for duplicate/invalid tickets to replace "positive review", which would IMHO be more appropriate or intuitive. -leif -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
