Trac

As OST is the client facing documentation, trac is the developer side container of problems, fixes needed, and enhancements.

If making a trac ticket for an unresolved OST concern, be sure to include the name, #, and URL in the 'internal notes' field on OST. This makes it direct for anyone to follow up and see if the blocker for the expressed problem has been resolved.

trac: https://qtrac.cns.utexas.edu/trac/wiki/WikiStart

Trac is a big shoebox stuffed full of notes, and it's pretty common for things to get overlooked here, so be sure to copy leta/ian/gsl and mention and speak up for anything that seems to warrant greater urgency.

How to make a trac ticket!

•Express only one specific problem per ticket
•Can look at #8916 for positive example (bad examples are vague, lack specificity of what the problem is, and provides no links on how/where to scout)

click New Ticket and include:

A description of the issue. The observed incorrect behavior, incorrect data, etc... (ex: problem-....)

A description of the expected correct behavior, correct data, etc... (ex: solution/desired outcome-...)

A link to a page(s) demonstrating the issue. Include URL's

A list of steps to re-create the issue (including all details–if masq as someone, who, what to click, not click, what to notice on each page)

Any error messages you see