https://forge-allura.apache.org/p/allura/tickets/You searched for labels:"export"enThu, 17 Mar 2016 15:23:05 -0000https://forge-allura.apache.org/p/allura/tickets/8064/The `with_attachments` param added in [#8052] should be added to `api.raml`. Also `allura/scripts/project_export` should be updated to have that as a script option.Dave BrondsemaThu, 17 Mar 2016 15:23:05 -0000https://forge-allura.apache.org/p/allura/tickets/8064/https://forge-allura.apache.org/p/allura/tickets/8063/Exporting with attachments ends up creating lots of empty directories that aren't necessary. And it'd be nice if the directories were named nicely, using the artifact `url` or `shorthand_id` when possible, and `_id` only when necessary.Dave BrondsemaWed, 09 Mar 2016 22:21:35 -0000https://forge-allura.apache.org/p/allura/tickets/8063/https://forge-allura.apache.org/p/allura/tickets/6920/The `bulk_export_download_instructions` text that is included in emails after an export should also be included in the success API result for a bulk export. Then users of the API will have instructions handy and not have to do a manual export to get them via email.Dave BrondsemaSun, 29 Mar 2015 18:10:16 -0000https://forge-allura.apache.org/p/allura/tickets/6920/https://forge-allura.apache.org/p/allura/tickets/6919/Make the Tools parameter when scheduling an export job optional and export all existing when it is missing, otherwise the backup Script needs to be changed every time a tool is added and manual things to do usually are forgotten regularly.Dave BrondsemaMon, 30 Jun 2014 20:33:52 -0000https://forge-allura.apache.org/p/allura/tickets/6919/https://forge-allura.apache.org/p/allura/tickets/6692/Currently difficulties in project exports are: * requires a manual form submission * email is used to notify when ready * resulting filename is non-deterministic It should be possible to automate a project export with a script, with minimal difficulty.Dave BrondsemaThu, 20 Aug 2015 22:07:10 -0000https://forge-allura.apache.org/p/allura/tickets/6692/https://forge-allura.apache.org/p/allura/tickets/6662/[forge:site-support:#5383] >I like the new Project Data Export feature, but what about attachments to wiki, ticket, or discussion items? Not that I really want these encoded into a JSON file, but this isn't really a complete "copy for safekeeping" if the export only has URLs to sourceforge.net for any attached images, patch files, etc. 1. We should put the attachments in a separate folder 2. We should make attachments optional, so folks won't get an enormous backup if they don't want itChris TsaiWed, 09 Mar 2016 21:43:49 -0000https://forge-allura.apache.org/p/allura/tickets/6662/https://forge-allura.apache.org/p/allura/tickets/6661/Forum posts don't include timestamps in the export, but they do in the API (e.g. https://sourceforge.net/rest/p/freertos/discussion/382005/thread/488af1de/). These should match.Dave BrondsemaThu, 20 Aug 2015 22:07:20 -0000https://forge-allura.apache.org/p/allura/tickets/6661/https://forge-allura.apache.org/p/allura/tickets/6619/Not all tickets are included in the export. And URLs aren't using the right domain. admin.json: ~~~~ ... "url": "http://localhost:80/u/jpschewe/", "username": "jpschewe", "name": "Jon Schewe" } ], "name": "Allura", "url": "http://localhost:80/p/allura/", "icon_url": "http://localhost:80/p/allura/icon", "screenshots": [ { "url": "http://localhost:80/p/allura/screenshot/allura-tickets.jpeg", ... ~~~~Dave BrondsemaThu, 20 Aug 2015 22:07:20 -0000https://forge-allura.apache.org/p/allura/tickets/6619/https://forge-allura.apache.org/p/allura/tickets/6614/It'll be a lot easier to export your whole project if there's a "check all" button on the export page.Dave BrondsemaThu, 20 Aug 2015 22:07:20 -0000https://forge-allura.apache.org/p/allura/tickets/6614/