Opened 9 years ago

Closed 9 years ago

Last modified 4 years ago

#1712 closed enhancement (fixed)

Archive Mixminion-* tasks

Reported by: karsten Owned by: erinn
Priority: Medium Milestone:
Component: Internal Services/Service - trac Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

We should archive the tasks belonging to the Mixminion-Server, -Client, and -Other components. I talked to Nick and he said he's fine taking them out if they're archived and available somewhere (with a not yet specified definition of somewhere). It looks like the three Mixminion-* components are the only components we're not likely to do any work on in the future.

Is there an easy way to export tasks belonging to these three components?

Child Tickets

Change History (3)

comment:1 Changed 9 years ago by nickm

This is nick, confirming that i am fine with archiving the mixminion bug tracker contents. It would be nice, assuming we're doing an automated export, to also export the closed bugs as well as the open ones.

I am assuming that we can do this and leave gaps in our ticket numbering, and that those gaps will not get filled in with new tickets. True? We do *not* want to reuse ticket numbers.

comment:2 Changed 9 years ago by erinn

Resolution: fixed
Status: newclosed

I've done this by deleting the components, creating query that finds all of the Mixminion-* tasks and have saved it as report 24: https://trac.torproject.org/projects/tor/report/24

Closing, reopen if you have any complaints.

comment:3 Changed 4 years ago by qbi

Component: TracService - trac

Move all tickets from trac to "Service - trac" component.

Note: See TracTickets for help on using tickets.