Jira Project Integration - Default Field Mappings and Scheduled Strategies

  • Updated

This article explains the Jira Projects to OnePlan Plans default field mappings for your integration.

To complete the Jira integration setup, you must complete:

Check the Field Mappings

After the integration is installed, it is best practice to check the default field mappings for errors or missing mappings.

After reviewing the field mappings, continue on to Jira Integration - Custom Types Settings.

Integration Information

OnePlan Changes

Once the integration is complete, three things will occur in the OnePlan integration page:

  1. An integration line item is made.
  2. An integration event is created.
  3. Jira is now available in the Connected Systems icon.

Integration Line item

Each item within the Integration section shows the OneConnect integrations connected to the OnePlan Work Plan.

Integration Event

Integration events are automated responses that will bring data over from OnePlan into Jira.

What this event does is trigger the OnePlanPublish strategy for any item that is connected to Jira. This will bring any values that are mapped to go from OnePlan to Jira to be updated.

What triggers this event is after a connected item has been saved in OnePlan. At the plan details page, this occurs after an item has been modified and then is automatically saved. At the backlog level, this is done after editing a field, and then clicking Save.

Connected Systems

Any item that is connected to Jira will show the Jira icon at both the My Portfolio page, and for any item in the Work Plan Backlog page for plans and tasks that are connected to Jira.

To connect an item from OnePlan into Jira, navigate to the Work Plan - Backlog page, click on the plug icon (Connected Systems Icon) and create a new item. Once the plan is connected, the Connected Systems window can also be used to Import, Export, or Open the Jira Plan level item.

 

Default Field Mappings

Plans - Projects

OnePlan Fields

Jira Fields

Direction

Notes

Jira Project Types

Project Types

Both

Required

Name

Project Name

Both

Required

Owner

Lead

Both

Required

Backlogs - Issues

OnePlan Fields

Jira Fields

Direction

Notes

Assigned To

Assignee

Both

Recommended

Item Type

Issue Type

Both

Recommended

Name

Summary

Both

Required

Parent Id (Structure)

Parent Issues ID

Both

Recommended

Status

Status

Both

 

Lookup Tables - Project Types

OnePlan Fields

Jira Fields

Direction

Notes

Jira Project Types (Plan)

Type Name

Both

Required

Default Scheduled Strategies

The following scheduled strategies are installed by default:

SynchJiraProjectTypes

SynchJiraProjectTypes will update the OnePlan choice field Jira Project Types by synchronizing the list of Jira Project Types.

OnePlanUpdate

Publish data from Jira to OnePlan.

This strategy will bring in all Jira Projects and their associated issues into OnePlan. It is recommended that a filter be put in place to limit what Projects are desired to be brought over. To facilitate large-scale data manipulation, this strategy now efficiently processes multiple records simultaneously. Additionally, for consistency and accuracy alignment between Jira and OnePlan, the strategy will automatically remove tasks from OnePlan if they are deleted in Jira. This deletion specifically applies to backlog items and does not affect plans within OnePlan. 

OnePlanPublish

Publish data from OnePlan to Jira.

This strategy will bring in all OnePlan Plans and their associated backlogs into Jira. It is recommended that a filter be put in place to only bring in Plans that have a Jira Project Type filled in be brought over to Jira for the strategy to not fail. 

Optional Strategies

OnePlanPlanItemsCleanUp 

Deletes OnePlan task/backlog items that have been deleted from Jira. This does not delete plans from OnePlan.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request