 |
 |
We're just using OSTicket for all tech requests, including web issues. Sent from my iPhone > On Jul 11, 2014, at 10:07 AM, Charlie Morris <[log in to unmask]> wrote: > > We (Web Team at NCSU Libraries) started using GitHub's issue queue to track > bugs and requests. I think it's catching on. It's free, it's popular > (good support), lets you assign people, lets you apply labels and > milestones for categorizing, lets you add to the issue via email or web > interface, lets you close an issue via git commit... emoji. It's pretty > nice. One problem is tracking issues that aren't necessarily related to the > code in the repo. That might be confusing, we're still working through > that. > > -Charlie > > >> On Fri, Jul 11, 2014 at 10:48 AM, Andrew Shuping <[log in to unmask]> wrote: >> >> Hey Elizabeth, >> >> I know my library's systems department uses The Trac project: >> http://trac.edgewall.org/, which lets them do exactly what you're asking >> about. I can't remember how easy/difficult the installation process is, >> but using it is easy for almost anyone. Our building maintenance person >> has even started using it as a way to track what she needs to do. >> >> Andrew Shuping >> >> Robert Frost - "In three words I can sum up everything I've learned about >> life: it goes on." >> >> >> On Fri, Jul 11, 2014 at 9:30 AM, Elizabeth Leonard < >> [log in to unmask]> wrote: >> >>> Does anyone have a good way to track requests to make changes to your >>> website(s)? I would like to be able to put in requests and be able to >> track >>> if they are done and when, so there's fewer emails flying about. >>> >>> E >>> >>> Elizabeth Leonard >>> Assistant Dean of Information Technologies, Resources Acquisition and >>> Description >>> Seton Hall University >>> 400 South Orange Avenue >>> South Orange, NJ 07079 >>> 973-761-9445 >>