Jira Project Integration - Default Field Mappings and Scheduled Strategies – Support

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.

This integration has these main use cases for functionality.

Create/Update project in Jira
On creation, user is able to select Jira project types
Create/Update plan in OnePlan
Create/Update backlog in OnePlan from Jira issue types associated with the connected project
Issue types synchronized are based on the ones specified in OneConnect

Plans - Projects

OnePlan Fields	Jira Fields	Direction	Notes
Name	Project Name	Both	Required
Jira Project Types	Project Types	Both	Required
Owner	Lead	Both	Required

Backlogs - Issues

OnePlan Fields	Jira Fields	Direction	Notes
Name	Summary	Both	Required
Parent Id (Structure)	Parent Issues ID	Both	Recommended

Lookup Tables - Project Types

OnePlan Fields	Jira Fields	Direction	Notes
Jira Project Types (Plan)	Type Name	Both	Required

The following scheduled strategies are installed by default:

SynchJiraProjectTypes - SynchJiraProjectTypes will synchronize the list of Jira Project Types to the OnePlan choice field 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.
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.