Update README

README.md

@@ -2,7 +2,12 @@
  [![Donate!](https://img.shields.io/badge/Donate-PayPal-green.svg)](https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=D5KHS5GJPJ5PQ&currency_code=BRL&source=url)
  [![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2Fnatenho%2Fgo-jira-migrate.svg?type=shield)](https://app.fossa.com/projects/git%2Bgithub.com%2Fnatenho%2Fgo-jira-migrate?ref=badge_shield)
 
-This tool can migrate team-managed project issues between two JIRA Cloud accounts. It migrates attachments, description, comments, images, links, custom fields and so on.
+This tool can migrate both company-managed and team-managed project issues between two JIRA Cloud accounts. It migrates attachments, description, comments, images, links, custom fields and so on by actually reading the original issue and creating a new one with the same details. The main purpose of this tool is the lack of support for migrating team-managed projects.
+
+## References
+
+- [CLOUD-11467 - Support the Migration of Team Managed projects](https://jira.atlassian.com/browse/CLOUD-11467)
+- [What migrates in a cloud-to-cloud migration for Jira](https://support.atlassian.com/migration/docs/what-migrates-in-a-cloud-to-cloud-migration-for-jira/)
 
 ## Usage
 
@@ -53,8 +58,9 @@ This example include some additional switches and custom fields to be migrated,
 
 ## Recommendations
 
-- Make sure the user has Administrator access to the target JIRA project
-- Make sure assignees and reporters have access to the target JIRA project
+- Create a dedicated user for the migration, so it can be easily identified
+- Make sure the user has Administrator access to the source and target JIRA projects
+- Make sure assignees and reporters have access to the target JIRA project. The tool will do a best effort to set those.
 - The target JIRA project must exist and must have the same issue types and custom fields
 - Make sure that attachment upload sizes are identical between the accounts (Refer to https://support.atlassian.com/jira-cloud-administration/docs/configure-file-attachments/ to configure limits)
 
@@ -64,6 +70,7 @@ This example include some additional switches and custom fields to be migrated,
 - Created issues are enriched with migration information, so it is easy to find a issue in the new JIRA project by the old key
 - The original issue will be linked to the created issue
 - Comments are all made by the migration user, mentioning the original user that wrote the comment
+- Created/Updated dates are lost because all issues are created at the moment of the migration
 
 ## License
 [![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2Fnatenho%2Fgo-jira-migrate.svg?type=large)](https://app.fossa.com/projects/git%2Bgithub.com%2Fnatenho%2Fgo-jira-migrate?ref=badge_large)