<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ticket search results</title><link>https://forge-allura.apache.org/p/allura/tickets/</link><description>You searched for assigned_to:"deniskkotov"</description><language>en</language><lastBuildDate>Wed, 09 Mar 2016 21:44:07 -0000</lastBuildDate><item><title>Backend support for attachments in exports</title><link>https://forge-allura.apache.org/p/allura/tickets/8051/</link><description>Update the export tasks with a flag for including attachments or not.  How to organize / reference the files in the export .zip is not determined yet, but is obviously important.

[#6662] will be the frontend for this.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Wed, 09 Mar 2016 21:44:07 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8051/</guid></item><item><title>Add attachments to Export [ss5383]</title><link>https://forge-allura.apache.org/p/allura/tickets/6662/</link><description>[forge:site-support:#5383]

&gt;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 it</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Wed, 09 Mar 2016 21:43:49 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6662/</guid></item></channel></rss>