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

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

The following video walks though the default field mappings for the Jira Epics and OnePlan Plans integration.

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 Epic level item type in Jira
On creation, user will be required to specify the Project where the epic will belong in Jira
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.

OnePlan Fields	Jira fields	Direction	Notes
Jira Project Names (Plan)	Project Names	Both	Required

The following scheduled strategies are installed by default:

SynchLookup - SynchLookup will synchronize the list of Project Names from Jira into the Jira Project Names dropdown within OnePlan.
OnePlanUpdate - Publish data from Jira to OnePlan.

This strategy will bring in all Jira Epics and their associated issues into OnePlan. It is recommended that a filter be put in place to limit what Epics are desired to be brought over.
OnePlanPublish - Publish data from OnePlan to Jira.

This strategy has a filter within the OnePlan – Jira > Plans – Epics section. This filter will only bring plans from OnePlan over to Jira if the Jira Project Names field has a value selected. If this filter is removed (and not replaced with an alternative filter), the strategy will fail for each plan that does not have this field filled in within OnePlan.