This article explains the Jira Spaces to OnePlan Plans default field mappings for your integration.
To complete the Jira integration setup, you must complete:
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.
OnePlan Changes
Once the integration is complete, three things will occur in the OnePlan integration page:
- An integration line item is made.
- An integration event is created.
- 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.
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 |
| Iteration (OnePlan System) | Sprint Name (With Board) | Both | Recommended |
| Name | Summary | Both | Required |
| Parent Id (Structure) | Parent Issues ID | Both | Recommended |
| Status | Status | Both | Value Mapping 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 retrieves the available Jira Project Types from Jira and updates the Jira Project Types choice field in OnePlan with those values.
OnePlanUpdate
Publish data from Jira to OnePlan.
This strategy has a filter within the Jira - OnePlan > Projects - Plans section. This filter will only bring each Jira Space over into OnePlan only if the item is already connected. If this filter is removed (and not replaced with an alternative filter), all Spaces (and the associated Issue Types listed) within the Jira Organization will be brought over into OnePlan.
This strategy will bring in all Jira Spaces and their associated issues into OnePlan. It is recommended that a filter be put in place to limit what Spaces 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 has a filter within the OnePlan - Jira> Plans - Projects section. This filter will only bring each Jira Space over into OnePlan only if the item is already connected. If this filter is removed (and not replaced with an alternative filter), all plans in OnePlan will attempt to be brought into Jira. These plans will fail to create in Jira if there is not a valid Jira Project Type set on each of the OnePlan plans.
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.
Optional Strategies
OnePlanPlanItemsCleanUp (Obsolete)
This strategy previously deleted OnePlan task/backlog items that had been deleted from Jira. Notably, this strategy did not delete plans from OnePlan.
Current Status:
This functionality has been fully incorporated into the OnePlanUpdate strategy, rendering this standalone strategy obsolete.
Comments
0 comments
Please sign in to leave a comment.