In this article you'll learn:
how to import boards and cards from Jira to FlowFast in a few steps;
what data can be imported from Jira to FlowFast and where to find it.
After it click on the plus button near the Spaces tab and then click «Create space».
Give your space a title and then click Create.
API Token authorization type
To authorize you'll need domain, email and API token.
Domain is your Jira address.For example, domain.atlassian.net
You can find it in the address bar of your browser while you're in your Jira account.
Then you need to insert the email address that is tied to your account in Jira.
API Token can be created if you follow this link and click «Create API token».
Label your token. The label can be any, you won't need to insert it anywhere.Then click Create.
Copy the token and insert it in the corresponding field in FlowFast.
Click «Next».
Password authorization type
This type of authorization is only available for Jira Server.
If you choose this authorization type you'll also need to insert your domain and email tied to Jira account.
Then type in your Jira account password.
Click «Next».
Choose Confluence spaces that you want to import. There will be created a separate folder for each space in the documents section in FlowFast.
If there are spaces you don't want to import you can click on a cross button near the space title.
The nested document structure of the Confluence space will be preserved..The data can be found in the «Documents» section in FlowFast.
Please note that in case a Confluence page has internal pages, a document will be created for that page, as well as a folder with the same name containing all internal pages.
You can use a separate option to import data from Confluence for a more detailed and systemized data import.
If you used various types in Jira we recommend to create additional boards for each type, as in FlowFast different boards are used for different levels of tasks in hierarchy. When you've finished configuration click «Next».
Option 1: Child issues will be reflected as check-list items in the main task in FlowFast.
For it, please, choose «Checklists» in the «Import Sub-tasks as» field while configuring board structure.
Option 2: Child issues will be imported as separate child cards tied to the main/parent task.
For it, please, choose «Cards» in the «Import Sub-tasks as» field while configuring board structure.
Then proceed with the board structure configuration. Choose where to reflect tasks and child issues (sub-tasks):
Click «Next». Child issues from Jira will be imported as child cards connected to the parent card.
You need to enter emails of the users in the corresponding fields. If you do it the ownership/membership in cards comments will be reflected in FlowFast after the migration.Т
Please note that Jira only provides user emails if the user account has this setting enabled. Otherwise, you need to insert emails manually. If you do not plan to invite a participant, you can skip this step. You can always invite users later.
As soon as it finishes FlowFast will send you an email notification. As a rule the import takes several minutes*.
Where to find Confluence documents:
The documents will be imported to the «Documents» section.
You can find it on the left-side panel:
Actions with boards after import:
You can add tags, due dates, card members, etc, and start the working process.
If you imported ll your boards to one space you can move boards to other spaces if you wish. For it please click on three dots in the right corner of the board.
Choose «Move board to other space».
Pick up the necessary space where you want to place the board or type in the name of a new space to create it.
Then click «Create space and move board», in case you create a new space.
Done! The board is now located on a new space.
Data from Jira | Where to find it in FlowFast |
Issue Resolution | Is imported in the field chosen in the import settings. |
Issue key | Is imported in the field chosen in the import settings. |
Issue history/ the changes of statuses of the issue (depending on the imported statuses) | Is reflected in the Card history. To open it press three dots in the right corner of the open card and choose «Show history» |
Issue type | Is imported as Card type. |
Issue description | Is imported as card description. |
Issue due date | Is imported as a Due date in a card. |
Issue start date | In case a Jira issue has both a start date and due date, there will be a «Timeline» property. It's reflected in the card itself and in the «Timeline» format of a space. |
Child issues | Can be imported as checklist items: Or can be imported as child cards: |
Linked issues — Blocked by | Are imported as blocks |
Linked issues — Relates to | Is imported as a link |
The relations of Epic with a card | Are imported as related cards (parent and child cards) |
Custom properties | Custom properties with the type «jira» The types of properties that are imported: paragraph, short text, number, date, timestamp, dropdown, labels. |
Attachments | Are imported as files within a card |
Comments | Are imported as comments in a card |
External links | Are imported as links in cards. In case Confluence is imported the links to Confluence documents are replaced with the links to FlowFast documents. |