Content Comparison

Do we need to migrate pull request details?

Github repositories also have pull requests marked raised by users. if we have to migrate them then they have to be migrated to Bitbucket cloud

No, There is no need to migrate repositories

Do we need to migrate the closed issues?

There are some closed issue present in the repository which somebody had already worked upon and have resolved them so do we have to migrate them also?

Do we have to create epics in Jira cloud for issues marked with label ‘epic’?

There are some issue with labels 'Epic' against them so do we have to create epic in Jira cloud for such issues?

Yes

Do we have to migrate users also?

There are users in the SiftScience accounts so Do we have to migrate these users too to Jira cloud?

Mapping between Github users and Jira users is required

What kind of ticket should we create in Jira for each issue in Github?

Github has only one issuetype called as issues and Jira has a separate field called as issuetypes, So how should we identify which one is a bug, task, story or any other type?

Open

What if the issue types doesn’t have any label?

Does client uses Jira cloud or after github migration they will start using it?

Wanted to understand whether Jira cloud is having data/configuration at present or not.

Client is already using Jira Cloud

Do we have list of labels that we need to support for migration?

The labels in Github should be migrated to Jira. Now Sift uses labels itself for different purposes. Some of them could be used to mark issuetypes like bugs and feature requests while others may be used for marking them with specific technology of development.

Yes we have the list

What if a issue in github is marked with two labels which are considered as different projects?

ex. if an issue AP-1 has two labels project 1 and project 2 under it in Github then while moving it to Jira under which Jira project should this issue be put? project 1 or project 2?