allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brondsema" <>
Subject [allura:tickets] #6541 Record import_id and audit log during imports
Date Thu, 05 Sep 2013 19:38:02 GMT
- **QA**: Dave Brondsema


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

**Status:** code-review
**Labels:** import 
**Created:** Thu Aug 08, 2013 09:17 PM UTC by Dave Brondsema
**Last Updated:** Wed Aug 28, 2013 08:54 PM UTC
**Owner:** Cory Johns

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 because is subscribed to

To unsubscribe from further messages, a project admin can change settings at
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message