#6740 Show more helpful info on import pages

v1.0.1
closed
General
2015-08-20
2013-10-04
No

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

Discussion

  • Dave Brondsema

    Dave Brondsema - 2013-10-04
    • Size: --> 1
     
  • Dave Brondsema

    Dave Brondsema - 2013-10-04

    And for our GC->SF download importer, files' summary & labels aren't recorded. Recommend creating README files.

     
  • Cory Johns

    Cory Johns - 2013-10-14
    • status: open --> in-progress
    • assigned_to: Cory Johns
     
  • Cory Johns

    Cory Johns - 2013-10-14
    • status: in-progress --> code-review
     
  • Cory Johns

    Cory Johns - 2013-10-14

    allura:cj/6740

     
  • Dave Brondsema

    Dave Brondsema - 2013-10-14

    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 files importer (which needs a bit added yet, see comment)

     
  • Cory Johns

    Cory Johns - 2013-10-14
    • status: code-review --> in-progress
     
  • Cory Johns

    Cory Johns - 2013-10-14

    allura:cj/6740
    forge-classic:cj/6740

     
  • Cory Johns

    Cory Johns - 2013-10-14
    • status: in-progress --> code-review
     
  • Dave Brondsema

    Dave Brondsema - 2013-10-14
    • status: code-review --> closed
    • QA: Dave Brondsema
     

Log in to post a comment.