How your Jira projects will look in Zepel
This article will help you understand what your Jira projects will look like after it is imported into Zepel.
Jira projects get imported into Zepel as projects.
All Jira Issues of type “Epic” get imported into Zepel as separate Feature.
All issues linked to epic will be imported as items inside the Feature. Additional properties (like status, estimate etc) of an Epic are lost when the epic is moved from Jira to Zepel.
Workflows from Jira get imported into Zepel as boards. Each workflow in the Jira project becomes a separate board. Each status of the workflow gets a unique column.
Note that workflows in Zepel have only one start state and one end state. During the import, the first start state in the JIRA workflow becomes the start state in Zepel. The End State with the most number of items in the Jira workflow gets chosen as the end state in Zepel.
|Due Dates||Due Date:
Due dates are maintained for every issue.
Estimates are migrated from Jira to Zepel (in points).
Issue status are maintained when issues are migrated from Jira to Zepel.
Assignees are migrated seamlessly from Jira to Zepel. In case an assignee on Jira is not a member of your team on Zepel, a new account is created and the user is notified via email.
Attachments are migrated from Jira to Zepel without any change.
Comments from Jira are migrated to Zepel. Comments in Zepel have a threaded structure. Issue level comments are imported from Jira and are attached to the appropriate issues.
|Jira Issue Types (Except Epic)||Item Types:
Stories, Bugs, Tasks and Subtasks are migrated and maintain their types in Zepel. Custom Issue types from JIRA are migrated as tasks with hashtags. For instance a custom issue type request will be imported as a task with hashtag #request
Issue Priorities from Jira are handled in Zepel via hashtags( #lowest, #low, #medium, #high and #highest).
Labels in Jira issues get converted into hashtags attached to issues on Zepel.