Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: allura-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of noreply@sourceforge.net
 designates 216.34.181.60 as permitted sender)
Content-Type: multipart/related;
 boundary="===============5307337759970356847=="
MIME-Version: 1.0
To: "Ticket 6541" <6541@tickets.allura.p.re.sf.net>
From: "Dave Brondsema" <brondsem@users.sf.net>
Reply-To: "Ticket 6541" <6541@tickets.allura.p.re.sf.net>
Subject: [allura:tickets] #6541 Record import_id and audit log during imports
Message-ID: 
 <5ebece2f54fefb5ff17c93e424aac8cbbd0e9f11.tickets@allura.p.sourceforge.net>
Date: Thu, 08 Aug 2013 21:17:55 +0000

--===============5307337759970356847==
Content-Type: multipart/alternative;
 boundary="===============6869779768223475913=="
MIME-Version: 1.0

--===============6869779768223475913==
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit


---

** [tickets:#6541] Record import_id and audit log during imports**

**Status:** open
**Labels:** import 
**Created:** Thu Aug 08, 2013 09:17 PM UTC by Dave Brondsema
**Last Updated:** Thu Aug 08, 2013 09:17 PM UTC
**Owner:** nobody

We should keep track of the original source in imported artifacts.  The import_id field is just right for that.  IIRC, tool configs may have an import_id too.  Both would be useful so that we could run reports on how my tickets or trackers (for example) have been imported from elsewhere.

Also record each import in the project audit log.


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.
--===============6869779768223475913==
MIME-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<div class="markdown_content"><hr />
<p><strong> <a class="alink" href="http://sourceforge.net/p/allura/tickets/6541/">[tickets:#6541]</a> Record import_id and audit log during imports</strong></p>
<p><strong>Status:</strong> open<br />
<strong>Labels:</strong> import <br />
<strong>Created:</strong> Thu Aug 08, 2013 09:17 PM UTC by Dave Brondsema<br />
<strong>Last Updated:</strong> Thu Aug 08, 2013 09:17 PM UTC<br />
<strong>Owner:</strong> nobody</p>
<p>We should keep track of the original source in imported artifacts.  The import_id field is just right for that.  IIRC, tool configs may have an import_id too.  Both would be useful so that we could run reports on how my tickets or trackers (for example) have been imported from elsewhere.</p>
<p>Also record each import in the project audit log.</p>
<hr />
<p>Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to <a href="https://sourceforge.net/p/allura/tickets/">https://sourceforge.net/p/allura/tickets/</a></p>
<p>To unsubscribe from further messages, a project admin can change settings at <a href="https://sourceforge.net/p/allura/admin/tickets/options.">https://sourceforge.net/p/allura/admin/tickets/options.</a>  Or, if this is a mailing list, you can unsubscribe from the mailing list.</p></div>
--===============6869779768223475913==--

--===============5307337759970356847==--