...
Question | Details | Clarification |
---|---|---|
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 | NA |
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? | |
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? | |
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 |
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. | Already using Jira Cloud |
Do we have list of labels that we need to support for migration? |
...