Details
-
Suggestion
-
Resolution: Fixed
Description
This page should be updated to clarify that the Bitbucket importer is no longer supported and that users need to use the JSON importer instead. It should also describe the changes necessary in order to make sure the file is imported into JIRA successfully:
1. The Bitbucket "issues" attribute, i.e.
"issues": [ { "status": "new", "priority": "major", "kind": "bug", "content_updated_on": null, "voters": [], "title": "A title for the issue", "reporter": "dmeyer", "component": null, "watchers": [ "dmeyer" ], "content": "A description of the issue", "assignee": null, "created_on": "2017-08-01T20:24:43.481898+00:00", "version": null, "edited_on": null, "milestone": null, "updated_on": "2017-08-01T20:24:43.481898+00:00", "id": 2 } ]
This needs to be wrapped inside of a "project" object in order for JIRA to successfully create project. So the above example needs to look something like this:
"projects": [ { "name": "A Sample Project", "key": "ASM", "description": "A description of the project", "type": "software", "template":"com.pyxis.greenhopper.jira:gh-scrum-template", "issues": [ { "status": "To Do", "priority": "major", "kind": "bug", "content_updated_on": null, "voters": [], "title": "My first issue!", "reporter": "dmeyer", "component": null, "watchers": [ "dmeyer" ], "summary": "issue from bitbucket", "assignee": "dmeyer", "created_on": "2016-11-03T06:31:17.395256+00:00", "version": null, "edited_on": null, "milestone": null, "updated_on": "2016-11-03T06:31:17.395256+00:00", "id": 1 } ] } ]
2. The project object, in addition to a name, key and description, requires a "type" field that can be "business", "software", or "service-desk", and a "template" field that should be supplied if "software" is selected. For a SCRUM project the template should be "com.pyxis.greenhopper.jira:gh-scrum-template" and for a KANBAN project the template should be "com.pyxis.greenhopper.jira:gh-kanban-template". The full list of templates available can be obtained from this private API https://yourjirasite.atlassan.net/rest/project-templates/1.0/templates.
3. Several fields need to be renamed in order to be mapped correctly to JIRA fields. A full list is already on the documentation page but this needs to be done manually in the JSON file and won't be handled in a wizard. Specifically:
| In Bitbucket Export | Rename to import to JIRA |
|---|---|
| title | summary |
| kind | issuetype |
| content | description |
4. You must verify that the statuses and issue types that your Bitbucket issues will map to have already been created in JIRA.