cocoaforge

What are non-devs allowed/supposed to do with trac tickets besides create them? For example, if I, a non-dev, spot a duplicate or otherwise invalid ticket, or a request for an already-existing feature, am I only allowed to comment on it, or is closing it OK, too?

(I'm referring specifically to tickets 600 and 629, but my question also applies more generally.)

Commenting and closing duplicates is great. It'll help us a ton if you can catch those. Be sure to be nice when you close it though.

For tickets if you put #number it'll link to a ticket number

For commits, if you put [number] it'll link to that checkin

Really the only thing we don't want non-devs doing is:
- Setting milestones
- Assigning tickets (unless the person to whom you're assinging it asked you to please assign it to him)

Anything else you can do to make trac more organized or easier to use is fantastic

evands wrote:Really the only thing we don't want non-devs doing is:
- Setting milestones
- Assigning tickets (unless the person to whom you're assinging it asked you to please assign it to him)

Anything else you can do to make trac more organized or easier to use is fantastic

Also, setting the priority. Too many people are like OMGTHISMUSTBEFIXEDNOWHIGHESTPRIORITY