User Tools

Site Tools


Sidebar

integration_hub:integrations:online_jira:start

Project Online & Jira

Project Online & Jira integration scenario is a two-way synchronization of Project Online project tasks with Jira issues.

:!: NOTE: Correct synchronization requires previous specific configuration of both instances.

How to start using the Integration Hub

Step 1

Verify “Integration Prerequisites” and install “Integraiton Hub” add-on from Atlassian Marketplace for JIRA.

For more details on the process of installation please refer to the MS Project Online Integration JIRA add-on installation article.

Step 2

Configure both environments - Project Online & Jira - to work with Integration Hub.

Detailed instruction on configuration can be found in the Setup Project Online - Jira integration scenario article.

Step 3

Use Integration Hub for scheduled synchronizations between your environments.

If any questions or difficulties arise please contact our support team in one of the following ways:

Integration Prerequisites

Project Online

The following custom fields should exist on the PWA:

  • Project level text custom field with the name Jira Project - this field defines the name of the destination project in Jira. This field is not required for the integration to work. If the project name is not provided, the destination project will be chosen by the name equal to the project name in Project Online.
  • Task level flag custom field with the name Sync To Jira - this is a task-level Flag custom field that defines whether a project task should be synchronized with a Jira issue. This field is required for the integration and should be manually created in the PWA.
  • Task level text custom field Jira Issue Type with a lookup table - this is a task-level Text custom field with lookup table that determines Jira issue type (‘Story’, ‘Epic’, ‘New Feature’, 'Task', ‘Sub-task’, 'Bug', 'Improvement'). This field is not required for the integration to work. If the value is not provided, “Task” or “Sub-task” issue type will be used accordingly.

Jira

  • Custom field with the name Sync To PO should exist in Jira - custom field that identifies whether a Jira issue should be synchronized with a Project Online project task. This field is required for the integration and should be manually created in the Jira environment and added to the appropriate screens of the Issues for synchronization.
  • Jira legacy mode - must be Disabled (Issues > ISSUE FEATURES > Time tracking > JIRA legacy mode).
  • In case Jira on premise - Integration Hub can be compatible with Jira on premise as well, on condition that Jira is accessible from the Internet. Jira app (add-on) is currently working only with Jira Cloud, so you will need to use SharePoint App (SharePoint App installation)

Integration Hub

The following integration scenarios should exist:

- Project Online & Jira integration

- Status Notifications (In case you want to receive email notifications about unexpected situations)

Permissions

For Project Online, the account that performs the integration should be granted with PWA Administrator and Site Collection Administrator permissions.

For Jira the account used for synchronization should be a member of default administrators group and use 'English (US)' locale.

Integration

Fields Mapping

Project Online Integration direction Jira
Custom field: Task.“Jira Issue Type”System field: Issue.IssueType
System field: Task.NameSystem field: Issue.Summary
System field: UnassignedTask.WorkSystem field: Issue.Estimated
System field: UnassignedTask.ActualWorkSystem field: Issue.Logged
System field: UnassignedTask.RemainingWorkSystem field: Issue.Remaining
System field:Task.AssignmentSystem field: Issue.Assignment
System field: Task.Assignment.WorkSystem field: Issue.Estimated
System field:Task.Assignment.ActualWork System field: Issue.Logged
System field: Task.Assignment.RemainingWorkSystem field: Issue.Remaining
System field: Task.FinishDateSystem field: Issue.DueDate
System field: Task.Assignment.ActualStartSystem field: Issue.WorkLog.DateStarted
Hierarchy: Task.ParentTaskIdHierarchy: Issue.ParentIssueId

⇔ Data can be synced in both directions

⇐ Data can be synced only in one direction

< Data can be synced only at the first migration of the Entity (On create)

→ Data can be synced only at the first migration of the Value of some parameter (On update)

Synchronized Data

Project Online and Jira projects matching is done by Project Name.

The following data can be synchronized during the tasks sync from Project Online Tasks to Jira Issues:

a) if Project Online is the origin system

- Task Name;

- Task.Work (if task without assignment), (only while first sync of the Task);

- Task.Actual Work (if task without assignment);

- Task.Remaining Work (if task without assignment);

- Assignments (emails) (One assignment in Online equals one separate Issue in Jira for that assignment);

- TaskAssignment.Work (if task with assignment), (only while first sync of the Task);

- TaskAssignment.Actual Work(if task with assignments);

- TaskAssignment.Remaining Work (if task with assignments);

- Jira Issue Type (‘Story’, ‘Epic’, ‘New Feature’, 'Task', ‘Sub-task’, 'Bug', 'Improvement');

- Task FinishDate (only while first sync of this value);

- Hierarchy structure;

b) if Jira is the origin system

- Summary
- Logged (Time Spent);

- Remaining (Remaining Estimate);

- Assignment (email);

- Jira Issue Type.

The following data can be synchronized during the tasks sync from Jira Issues to Project Online Tasks:

a) if Jira is the origin system

- Issue Summary;

- Logged (Time Spent);

- WorkLog.Date Started (Date and Time);

- Remaining (Remaining Estimate);

- Due Date;

- Assignment;

- Issue Type;

- Hierarchy structure;

b) if Project Online is the origin system

- Issue Summary;

- Logged (Time Spent);

- WorkLog.Date Started;

- Remaining (Remaining Estimate);

- Assignment (email);

- Issue Type;

- Hierarchy structure;

integration_hub/integrations/online_jira/start.txt · Last modified: 2018/03/09 05:53 by Anita Boiadzhian