This article covers an upcoming feature in Birdview PSA.
Please wait for an official announcement about its release.
The Jira-Birdview integration app is designed to help Birdview PSA users transfer their Jira projects, issues, users, etc. to Birdview PSA and back.
The complete guide on the installation and configuring the JIRA integration app will be provided later.
Jire Permissions Required
To be able to operate the integration app the user must have the following permissions in Jira:
- View email addresses of users;
- Administer jira projects.
Birdview PSA Permissions Required
- Manage System Settings;
- Add projects.
Actions Available in the App
- The app returns a list of existing Jira projects.
- Selected Jira projects are imported to Birdview PSA and created as projects.
- Jira issues are imported to Birdview PSA along with their projects.
- Imported Jira issues are created as activities under respective projects. See the imported activity hierarchy below.
- All existing Jira users are imported to Birdview PSA unless they already exist. The mapping is via the user's email and login in Birdview (similar to SSO users authentication).
- A user added to Jira is imported to Birdview PSA unless it exists already. The mapping is via the user's email and login in Birdview (similar to SSO users authentication).
- Assignments of Jira issues are set up as assignments of respective Birdview activities.
Number of Issues per Project Limitation
In the current version, not more than 600 issues per project may be imported.
Imported Activity Hierarchy
The hierarchical structure of the issues imported to Birdview PSA as activities is based on the Jira issues' hierarchy, namely:
- Jira Epics are created as top-level activities in the Birdview projects;
- Jira stories, bugs and other types of issues that belong to Jira Epics are created as nested activities in Birdview.
- Jira stories, bugs and other types of issues that do NOT belong to Jira Epics are created as top-level activities under respective Birdview projects.
- Jira sub-tasks are created as nested activities in Birdview.
Field Mapping Used in the App
The rules of mapping Jira fields to Birdview ones used in the integration app are fixed and not configurable:
|Field Level||Jira Field||Birdview Field||Comment, *)|
|1. Project*)||Name||Name||*) Projects are created with the following defaults: status: Open; priority: Medium; Workflow: Default.|
|Project Lead||Creator||If the user does not exist it is created in Birdview|
|2. Issue*)||Summary||Name||*) Activities are created with the following defaults: status: Open; type: Task; priority: Medium.|
|Description*)||Descriptions||*)Mentions in descriptions are ignored.|
|Estimated hours*)||Estimated hours||*)If Jira Estimation Statistic is set to Time Tracking.|
|Estimated hours||Hours Left|
|Reporter||Creator||If the user does not exist it is created in Birdview.|
|Assignee*)||Assignee**)||*) 1 assignee per issue.
**) With default role. If the user does not exist it is created in Birdview.
|3. User*)||Name||Name||*) Users are created with the following defaults: role: Participant; status: Can't login; login: Email|
|Email is used as the Birdview login.|
To import projects from Jira:
- Click through Login picture > Company Settings > Integrations > Manage Apps.
- Click Edit Settings on the Jira app plaque.
- Click Select projects under Projects.
- Checkmark Jira projects to import.
- Click Save when done.
Disconnecting & Uninstalling the App
To disconnect the app, follow the steps below:
- Click Edit Settings.
- Click Disconnect.
To uninstall the app:
- Sign in to Jira.
- Click Apps.
- Select Manage apps.
- Click the Birdview integration app.
- Click Uninstall.