added limitation docs (#265)

* added limitation docs

* updated limitation doc

Co-authored-by: Akshay H <aksh-h@users.noreply.github.com>

docs/Limitations.md

@@ -0,0 +1,19 @@
+# Limitations of Azure DevOps Demo Generator
+
+Azure DevOps Demo Generator is to create a demo set up with predefined templates, it has some limitations, which are listed below. This can't be treated as migration or copying project tool from one Organization to another.
+
+## Following are the limitations of Azure DevOps Demo Generator and Template Builder
+
+|||
+|------|-----|
+|Custom process template| Templates with Custom Process doesn't supports for Kanban board setting or the style. To use the project template generated from Custom Process, organization must have the same process and  template Id|
+| Iterations| Not all the iterations can be exported by the Template Builder with hierarchy|
+|Iteration dates| It has predefined logic to align the dates, this can't be changed based on the requirement |
+| Work Items | Not all the work items will be exported. This count is limited to 200 work items of each type, if there are more than 200 work items |
+|Work Item fields|Only few standard fields are supported, which are listed below. ```Title, State, Reason,Priority, Steps, Parameters, LocalDataSource, AutomationStatus, AcceptanceCriteria, Tags, RemainingWork, AssignedTo,  AreaPath, Description, Effort```|
+| Wiki and Dashboard | These are not supported for General templates, we have some set of standart templates, which supports Wiki and Dashboard|
+|Test Plans and Suites| Not supported for General templates, supported for standard templates which demonstrates the feature|
+|Service connections|Service connections will be created based on the template requirement, those are needs to be authenticated by the user upon creating project|
+|Source code| Source code can be present in public GitHub repository, which can be imported at the time of project creation, if the source code present in some Azure Repos, user has to provide PAT in ```/Template/ServiceEndPoints/**.json``` files at the time of importing the template, as shown below ```"username": "$username$","password": "$password$"``` |
+|||
+

docs/Using-The-Template-Extractor.md

@@ -34,7 +34,7 @@ Setup an Azure DevOps project and make sure it is ready to be extracted. The ext
 
     ![Downloadin the generated template](./About-Azure-DevOps-Demo-Generator/images/generatedfile.png)
 
-**Note:** The Extractor does not support all item types and so it should not be considered as a migration tool for moving projects from one server to another. For what's supported and what's not supported, see the [limitations]() section
+**Note:** The Extractor does not support all item types and so it should not be considered as a migration tool for moving projects from one server to another. For what's supported and what's not supported, see the [limitations](./Limitations.md) section
 
 ## Provisioning your project from your custom template
 

docs/_site/extractor.htm

@@ -71,7 +71,7 @@
   </li>
 </ol>
 
-<p><strong>Note:</strong> The Extractor does not support all item types and so it should not be considered as a migration tool for moving projects from one server to another. For what’s supported and what’s not supported, see the <a href="">limitations</a> section</p>
+<p><strong>Note:</strong> The Extractor does not support all item types and so it should not be considered as a migration tool for moving projects from one server to another. For what’s supported and what’s not supported, see the <a href="/Limitations.md">limitations</a> section</p>
 
 <h2 id="provisioning-your-project-from-your-custom-template">Provisioning your project from your custom template</h2>