Skip to content

Commit

Permalink
Deployed 6db5210 with MkDocs version: 1.5.3
Browse files Browse the repository at this point in the history
  • Loading branch information
simonhbor committed Dec 8, 2023
1 parent 894011c commit 69bba6c
Show file tree
Hide file tree
Showing 5 changed files with 232 additions and 228 deletions.
5 changes: 3 additions & 2 deletions About/release-notes-addons-1/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -7862,7 +7862,7 @@ <h1 id="release-notes-for-spira-addons">Release Notes for Spira Addons<a class="
<h2 id="december-2023">December 2023<a class="headerlink" href="#december-2023" title="Permanent link">&para;</a></h2>
<ul>
<li>
<p>**<a href="../../External-Bug-Tracking-Integration/Using-SpiraTeam-with-Jira-Cloud">Jira Cloud DataSync</a> v6.0 and - **<a href="../../External-Bug-Tracking-Integration/Using-SpiraTeam-with-JIRA-5+">Jira Server DataSync</a> v6: these updates includes a number of enhancements and bug fixes:</p>
<p><strong><a href="../../External-Bug-Tracking-Integration/Using-SpiraTeam-with-Jira-Cloud">Jira Cloud DataSync</a> v6.0</strong> and - <strong><a href="../../External-Bug-Tracking-Integration/Using-SpiraTeam-with-JIRA-5+">Jira Server DataSync</a> v6</strong>: these updates includes a number of enhancements and bug fixes:</p>
<ul>
<li>Add support for JIRA estimate fields [IN:6345]</li>
<li>Add the ability to sync requirements and not import new incidents with a new dedicated "NoIncidents" sync mode [IN:6341]</li>
Expand All @@ -7876,8 +7876,9 @@ <h2 id="december-2023">December 2023<a class="headerlink" href="#december-2023"
</ul>
</li>
<li>
<p><a href="../../External-Bug-Tracking-Integration/Using-SpiraTeam-with-Jira-Cloud/#jira-configuration-helper">Jira Configuration Helper</a> adds the ability to filter statuses by project [IN:8686]</p>
<p><a href="../../External-Bug-Tracking-Integration/Using-SpiraTeam-with-Jira-Cloud/#jira-configuration-helper">Jira Configuration Helper</a>: adds the ability to filter statuses by project [IN:8686]</p>
</li>
<li><a href="../../Migration-and-Integration/Migrating-from-Jira">Jira Migration Tool</a> : fixes not being able to import users from Jira due to breaking changes in Atlassian's APIs [IN:8840]</li>
</ul>
<h2 id="may-2023">May 2023<a class="headerlink" href="#may-2023" title="Permanent link">&para;</a></h2>
<ul>
Expand Down
9 changes: 6 additions & 3 deletions Migration-and-Integration/Migrating-from-Jira/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -7950,10 +7950,13 @@


<h1 id="migrating-from-atlassian-jira">Migrating from Atlassian Jira<a class="headerlink" href="#migrating-from-atlassian-jira" title="Permanent link">&para;</a></h1>
<p>This section outlines how to use the included Migration Tool for importing projects, versions, requirements, issues, tasks and associated attachments from Atlassian Jira to SpiraTeam.</p>
<p><em>Note: This migration tool works with Jira Cloud, Server and Data Center editions.</em></p>
<p>This guide explains how to use Inflectra's "Jira Migration Tool" for importing projects, versions, requirements, issues, tasks and associated attachments from Atlassian Jira to SpiraTeam. This tool works with Jira Cloud, Server and Data Center editions.</p>
<div class="admonition info">
<p class="admonition-title">Advanced Migration</p>
<p>If the functions of this migration tool are not sufficient for your needs, please consider using our "<a href="https://github.com/Inflectra/spira-jira-migration-advanced">Advanced Jira to Spira Migration Tool</a>". This is an open source tool specifically for migration from Jira Server/DataCenter. It is developed by Inflectra's partner Tietoevry.</p>
</div>
<h2 id="installing-the-jira-migration-tool">Installing the Jira Migration Tool<a class="headerlink" href="#installing-the-jira-migration-tool" title="Permanent link">&para;</a></h2>
<p>This section outlines how to install the migration tool for Jira onto a workstation so that you can then migrate whole projects from Jira to either SpiraTeam or SpiraPlan (hereafter referred to as SpiraTeam). It assumes that you already have a working installation of SpiraTeam v6.0 or later and a working version of Jira Cloud, Server or Data Center. </p>
<p>This guide outlines how to install the migration tool for Jira onto a workstation so that you can then migrate whole projects from Jira to either SpiraTeam or SpiraPlan (hereafter referred to as SpiraTeam). It assumes that you already have a working installation of SpiraTeam v6.0 or later and a working version of Jira Cloud, Server or Data Center. </p>
<div class="admonition warning">
<p class="admonition-title">Minimum Version of Spira</p>
<p><strong>You must be on at least SpiraTeam 6.13 to use this tool</strong>. If you have an earlier version of SpiraTeam you will need to upgrade to at least v6.13 before trying to migrate projects.</p>
Expand Down
2 changes: 1 addition & 1 deletion search/search_index.json

Large diffs are not rendered by default.

Loading

0 comments on commit 69bba6c

Please sign in to comment.