Import from JIRA | Zoho Sprints Help

Import from JIRA

If you're a JIRA user, you can easily transfer your data to Zoho Sprints in a secure manner.

Before importing, you need to know the following:
  1. You need to have a JIRA Software account to import data for JIRA cloud.
  2. Only a workspace owner or admin can carry out the configuration.
  3. If you are on a free plan, you will only be able to import for 15 days from the day you activated your plan. You can upgrade your account to continue importing data when the trial expires.
  4. You cannot import more than 25 projects at a time.
  5. You can only process one import at a time.
  6. To import a project data, the Jira user who authorizes the import should have project administrative privilege in the project which should be imported. 
  7. To import users, email visibility should be enabled. Learn more
  8. When importing issues or work items with custom fields from Jira, ensure that the identical custom fields are created in Zoho Sprints beforehand. This allows you to seamlessly map them during the field-mapping stage of the import process. Learn more
  9. Ensure to enable Sprints in the Jira project before import is initiated. Import fails if Sprints is disabled. To enable it, navigate to Space Settings > Features > Enable Sprints. 

Add JIRA domain and configure account access in Zoho Sprints    

To add the JIRA domain:

  1. Go to Zoho Sprints.

  2. Click the gear icon at the top-right corner. The settings window will appear.

  3. Click Project under Imports.

  4. Select JIRA.

  5. Copy and paste your JIRA domain in the text box. (Refer to the GIF in settings page)

  6. Click Continue to proceed to configuration.

  7. JIRA application form appears in Sprints with the following details:

    1. Application URL

    2. Consumer key

    3. Consumer name

    4. Public key 

  8. Click the Go to JIRA button. You will be directed to the Application links page in JIRA.

  9. Click the Create link button.

  10. Select Direct Application Link as Link Type in the Create an application link form.

  11. Copy the Application URL from Zoho Sprints and paste it in JIRA. Now, click Next and, then click Continue.

  12. Enter the Application Name in the Review link form.

  13. Scroll down and select the Create an incoming link checkbox and click Continue.

  14. Now, copy the Consumer key, Consumer name, and Public key (available in Zoho Sprints JIRA settings page) and paste it in JIRA and click Continue. Now, your JIRA account is all set with Zoho Sprints configuration.

  15. Switch to Zoho Sprints and click Done.

  16. Agree to the terms and privacy policy of JIRA to import data from JIRA to Zoho Sprints.

  17. Click the Allow Access button.

  18. Click Allow to authenticate Zoho Sprints. You are ready to import from JIRA.

Import Projects from JIRA 

After authenticating, you'll be able to view all the projects available in JIRA in Zoho Sprints.

  1. Select the projects to be imported.
  2. Click Map Fields & Import. 

  3. Select the required layout and map the respective fields.
  4. Click Continue.
  5. Select the Notify all the new users checkbox if necessary and click Proceed.
    The import will be initiated.
When a project is imported, you'll receive an email and feed notification and then the next project import is initiated. This goes on until all the projects are imported. You can access the imported projects from the Projects tab in Zoho Sprints.  The imported projects can be accessed from the All Projects tab in Zoho Sprints.

Notes
  1. You can import work items and epics (issue type) from JIRA. 
  1. While importing the projects, the inline attachments added to item description, comments, and epic comments also get downloaded.

  2. When an import of five projects is initiated, and due to some reason, the third project fails to import, the following projects to be imported will also fail. Once the issue is resolved, you can reinitiate the import process for the failed ones. 
  1. Business type projects in Jira will be imported as Kanban type projects in Zoho Sprints. 

  2. Software type projects in Scrum or Kanban agile framework can be imported with the same framework in Zoho Sprints. 

Feature behavior

  1. While importing data from Jira, epic attachments and sub tasks whose parent is an epic will not be imported. 

Module mapping between JIRA and Zoho Sprints

JIRA Module
 Zoho Sprints Module
Projects
Projects
Users
Users
Issue type - Epics
Epics
Sprints
Sprints
Issues
Work Items
Log Work
Log Hours
Statuses
Item Statuses
Priorities
Item Priorities
Issue Types
Item Types
Comments
Comments
Attachments
Attachments
Labels
Tags
Versions
Releases

Notes
Note:
If a link exists between any two issues (excluding Epic-type issues) in a given Jira project, the same link will be maintained while importing the issues into sprints. 

. If a link exists between any two issues (excluding Epic-type issues) in a given Jira project, the same link will be maintained when the issues are imported into sprints.

Default field mapping between Jira and Zoho Sprints for Work Items 

Jira
Sprints
ID
ID
Name
Name
Description
Description
Type
Type
Priority
Priority
Status
Status
Reporter
Created by
Assignee
Assignee
Created on
Created on
Issue fix versions
Releases
Labels
Tags
Original Estimate
Duration
Story points or Story point estimate
Estimation Point
Sprint
Sprint
Epic
Epic 

Notes
Note:
When the 'Original Estimate' field of Jira is mapped with the 'Duration' field in Zoho Sprints, the work-hour (Work hours and Work days) settings of both products should be the same. For instance, if you have set eight working hours per day in Jira, the same eight hour work duration should be set in Zoho Sprints as well. Likewise, if the number of working days is set as five in Jira, the same should be set in Zoho Sprints as well. 

Import custom fields from JIRA

You can import custom fields from JIRA into Zoho Sprints. Custom fields enable you to capture data that is unique to your business or requirement. Learn more. 

To map JIRA custom fields to Zoho Sprints custom fields, you need to:
  1. Create a layout in Zoho Sprints that matches the custom fields available in JIRA.
  2. Have the custom fields in a single work item layout so that the layout can be selected while mapping JIRA custom fields.
  3. Select the congruent JIRA custom field for each Zoho Sprints custom field.
  4. Ensure that the mapped field types are the same. For instance, you need to map a multi select field type in JIRA only with a multi select field type in Zoho Sprints.
  5. Ensure the options in the picklist of both JIRA and Sprints custom fields are the same to avoid data mismatch. For instance, if a picklist field in JIRA has options A, B, and C, the same picklist options must be available in the mapped Sprints picklist field.
Notes
  1. To map epic custom fields, you need to create matching epic layout in Zoho Sprints and follow the same process as work item custom field mapping.
  2. The system auto-populates the data in custom fields in Zoho Sprints with the equivalent custom field in JIRA in the field mapping screen.
  3. Cascading custom fields can be imported from JIRA to Zoho Sprints. If the cascading custom fields are imported to Zoho Sprints, two picklist fields should be created in Zoho Sprints and mapped against the cascading custom field. For example, the cascading field name is Country, then two fields should be created - one as "Country - Parent" and the other as "Country - child".
  4. The People custom field can be imported from Jira to Zoho Sprints. The people custom field can be either a single user pick list field or multi-user pick list field. While importing, the system checks if the 'Restrict to a single person checkbox' is selected for this field in Jira. Based on this selection, Zoho Sprints dynamically chooses to use either 'User pick list' or 'Multi user pick list'. 

Custom field type mapping between JIRA and Sprints


Sprints Field Type
JIRA Field Type
Text
Short Text/Plain Text
HTML
Paragraph/Multiline Text
Date
Date Picker
Date Time
 Date Time Picker
Decimal
Number
Picklist
Select List (Single Choice)
Multi Picklist
Select List (Multi Choice)
Checkbox
Checkboxes
Radio
Radio
URL
URL
User Picklist
User Picker (Single User)
Multi User Picklist
User Picker (Multi User)
User Picklist (if Single user in Jira)
 People Picklist (Single user or Multi user)
Multi User Picklist (if Multi user in Jira)

Notes
  1. Third party picklist (single) or radio field can be mapped against Zoho Sprints picklist (single) or radio field. Likewise, multi-picklist or checkbox can be mapped against Zoho Sprints multi-picklist or checkbox field.

Modify email visibility in JIRA

If you are unable to import the project users, you might have to modify the email visibility in JIRA.
For JIRA cloud
  1. Navigate to  https://id.atlassian.com/manage-profile/profile-and-visibility
  2. Select "Anyone" in the Contact Section against the Email Address field . (Currently, it will be enabled as 'Only to you and admins'. Modify to 'Anyone') 

Once the import is successfully accomplished, all the JIRA users can login using their individual credentials and restore the Email Visibility using the above steps.

For JIRA server

The email visibility setting for JIRA server can be modified only by the administrator.
  1. Click Settings from the top-right corner.
  2. Select System .
  3. Go to Email Visibility under Options section.
  4. Select "Public" or "Show to logged in users" options.
Once the import is successfully accomplished, the JIRA administrator can login and restore the Email Visibility using the above steps.