#8998 closed enhancement (wontfix)
Export tickets to files
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | general | Version: | 0.11-stable |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
How is it possible to export tickets to the files. Is it possible to build a query that would export each ticket in a separate file or at least all the tickets in a single file.
Attachments (0)
Change History (4)
follow-up: 2 comment:1 by , 15 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Summary: | Экспорт всех билетиков в файл → Export tickets to files |
comment:2 by , 15 years ago
follow-up: 4 comment:3 by , 15 years ago
Ok, so it's a duplicate. OTOH, using the model API to export the data in a use-case specific format is probably easier for the OP than parsing RDF…
comment:4 by , 15 years ago
Replying to rblank:
Ok, so it's a duplicate.
It's also somehow related to DistributedTrac and the idea to have a distributed store to keep the data, the db being used as a "cache" but not as the primary data container.
It's not possible out-of-the-box, but it's quite simple to implement. As there's no standard format for representing tickets as files, this will be highly dependent on the use case. A standard implementation in Trac core is therefore hardly possible, hence closing as "wontfix".
The API for accessing the database is described in TracDev/DatabaseApi, and the model objects (
Ticket
in particular) in TracDev/DataModels#Ticket. That should hopefully get you started. If you need any help, please ask on the MailingList or the IrcChannel.