I like it, but think it might be best as stored per-tool. Then it can be displayed on the individual import forms, and optional importers E.g. wiki which isn't bundled with allura, and the SF-specific downloader (which needs a bit added yet, [see comment](./#2863))
--- ** [tickets:#6740] Show more helpful info on import pages** **Status:** code-review **Labels:** import **Created:** Fri Oct 04, 2013 05:29 PM UTC by Dave Brondsema **Last Updated:** Mon Oct 14, 2013 05:57 PM UTC **Owner:** Cory Johns There are several fields on project import pages so "URL Name" should be "PRODUCTNAME URL Name" so it's clear that field is for the destination. We should include extra notes on all the specific importers (both project & individual forms) regarding their caveats. These come to mind: * google code: home content not imported (its not part of the wiki) * google code repo: if project has multiple repos, only one is imported * google code tickets: private tickets not imported * github wiki: no wiki images or internal files, syntax for .rst and some other formats not supported, see https://sourceforge.net/p/allura/tickets/6534/?limit=10&page=1#2467 --- 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.
