id,summary,reporter,owner,description,type,status,priority,milestone,component,resolution,keywords,cc 316,Reference documentation for those with elevated Trac privileges,danielbachhuber,kpdesign,"This ticket might just have a target of one, me, but I'm thinking it would be nice to have reference documentation for those who have elevated Trac privileges. In Trac, I can do all of this: [[Image(https://dl.dropboxusercontent.com/s/kacdr7vc8bh60wx/2014-02-06%20at%2011.14%20AM.png)]] The [https://make.wordpress.org/core/handbook/trac/#ticket-properties existing Trac documentation] is a good reference point for what fields mean. For the most part, it's descriptive of how you use each field to describe different values. However, some fields require decisions to be made: Milestone, Resolution, and Priority. The [https://make.wordpress.org/core/handbook/trac/#triaging-and-punting Triaging and Punting] documentation starts to cover how new tickets are addressed, but doesn't go into enough depth (at least for me). I guess my questions are: * At what point does a ticket go from ""Awaiting Review"" to a given release milestone, or ""Future Release""? * If a ticket ends up in ""Future Release"", what does it need to end up in a release milestone? * Besides marking tickets as duplicate, which is mostly obvious, what is the decision making process to close a ticket as wontfix or maybelater? Context: I came across a 10 month old ticket of mine this morning (#WP24170) that I'd like to get a decision on (commit or punt) and realized I don't know the process. Well, I know the process as ""ping someone in IRC"" or ""try to make a core chat."" I'd also like to help go through all of the tickets ""Awaiting Review"" to help move them along.",enhancement,closed,normal,,Handbooks,fixed,close,