Allow content renaming on import
We prefer to maintain two instances of each piece of content, one using our production database connection, which has more complete data for users, and then second using our test connection which we use to prepare for DB changes ahead of time.
We currently do this by exporting content, importing it back, and changing the connection source and name. Adding the ability to rename reports on import would facilitate this process. We rename so that it is apparent which version of the content is the test report and which is the production.