Opened 14 years ago

Closed 13 years ago

#125 closed enhancement (fixed)

Set up issue tracking for private scripts.mit.edu Trac tickets

Reported by: andersk Owned by:
Priority: blocker Milestone:
Component: misc Keywords:
Cc:

Description

Keeping private issues in memory and secret zephyr classes is lossy. We should set up a private Trac or add a plugin to the existing Trac that lets us keep private tickets.

Change History (9)

comment:1 Changed 14 years ago by andersk

One of the plugins we could try is ​http://trac-hacks.org/wiki/SensitiveTicketsPlugin .

comment:2 Changed 14 years ago by andersk

  • sensitive set to 0

Now that this doesn’t break unrelated tickets, are we happy with this implementation?

comment:3 Changed 14 years ago by mitchb

  • sensitive changed from 0 to 1

comment:4 Changed 14 years ago by mitchb

foo

comment:5 Changed 14 years ago by andersk

  • sensitive changed from 1 to 0

comment:6 Changed 14 years ago by adehnert

FWIW, #126 is also lying around (and closed at the moment) as a test ticket.

comment:7 Changed 14 years ago by andersk

My SensitiveTicketsPlugin? ​patch (to stop ticket #1 from complaining that ticket #393622 doesn’t exist) was accepted upstream yesterday. We still need to solve the email and zephyr problem.

comment:8 Changed 13 years ago by geofft

Can I just create another Trac instance?

comment:9 Changed 13 years ago by geofft

  • Resolution set to fixed
  • Status changed from new to closed

Removed SensitiveTicketsPlugin? because it doesn't work.

I also created a text file in /mit/scripts/Private that holds bugs and outstanding scripts-root support requests for now; how we do something fancier depends on how concerns regarding whether this should be a scripts-hosted webapp at all are resolved.

Note: See TracTickets for help on using tickets.