OnePlan

OnePlan & Jira: Epics

Updated Jan 22, 2020

This article explains how to set up the integration between your OnePlan group/environment and Jira.  There are two different available integrations between OnePlan and Jira.  The use case for this article is the integration for OnePlan Plans mapped to Jira Epics.  

OnePlan Setup

In order to do the OnePlan setup, you need to be an admin, meaning you are a user with Owner permissions in OnePlan.

 

  1. Log in to your OnePlan group with your Office365 account.
  2. Open the Admin pages by clicking on the Settings gear.
  3. Select Integration in the admin navigation.  
  4. Click the + (plus) icon in the Authentication Keys section.
  5. Save the key name & generated key somewhere (such as in a notepad doc), as once you navigate away, the key cannot be seen.  To be used at a later step in the OneConnect configuration.

Jira Setup

  1. Navigate to the Jira site URL to be connected (i.e. https://instance.atlassian.net/).
  2. Follow the instructions to ‘Create an API token’ from this Jira document: https://confluence.atlassian.com/cloud/api-tokens-938839638.html
  3. Save the API token that is generated.  To be used at a later step in the OneConnect configuration.

OneConnect Setup

  1. Navigate to https://my.oneconnect.ai.
  2. Click Add Integration.  
  3. Select the OnePlan & Jira connector.  
OneConnect - Google Chrome

There are two available integrations between OnePlan and Jira.  Be sure to click the Configure button for Jira Epics and OnePlan Plans.  

ONEPLAN

  1. Authentication Key: Enter/paste the OnePlan Key that you saved from the earlier OnePlan Setup steps.
  2. Click the Next button.

INTEGRATOR

  1. Click the Next button.

JIRA

Input the Jira authentication information and configure the settings as required.

  1. Jira URL
  2. Username
  3. Password: API Token (Saved from earlier step above)
  4. Issue Types.  Specify the issue types to synchronize back into OnePlan as backlog items.  Task, Bug, Story, etc.
  5. Epic Type.  Specify the type of issue at Epic level. Plan from OnePlan will be created as the specified type in Jira.
  6. Check this option to bring all issues regardless if they are in sprint or not.  By default, will only bring issues that are in sprint.
  7. Check this option to roll up sub-tasks’ resources to the parent tasks.
  8. Click Next when ready.  Wait for the integration to finish the installation process and it will direct you to your integration.

Integration Information

Functionality

This integration has these main use cases for functionality.

  1. Create/Update Epic level item type in Jira
  2. On creation, user will be required to specify the Project where the epic will belong in Jira
  3. Create/Update plan in OnePlan
  4. Create/Update backlog in OnePlan from Jira issue types associated with the connected project
  5. Issue types synchronized are based on the ones specified in OneConnect

Scheduled Jobs

The following scheduled jobs are installed by default.  

  1. SynchLookups
    • Used to synchronize “Project Names” and “Jira Issue Priority” as choice values in OnePlan
  2. OnePlanUpdate
    • Create/Update plan in OnePlan
    • Create/Update backlog in OnePlan
  3. OnePlanPublish
    • Create/Update Epic level item type in Jira

Default Fields Created

In OnePlan:

  • Jira Project Names
    • Created on the Plan level field and is used for specifying which Project the plan will belong in Jira (Epic Level)
    • Type: Choice field
    • SynchLookup will be the job that runs the synchronization to fill out the project types

Default Field Mappings

Plans (OnePlan) <--> Epics (Jira)

OnePlan Fields

Jira Fields

Name

Epic Name

Jira Project Names

Project Name (Epic)

Backlog (OnePlan) <--> Issues (Jira)

OnePlan Fields

Jira Fields

Name

Summary

Parent ID (Structure)

Parent Issues ID

Lookup Tables (OnePlan) <--> Lookup Epics

OnePlan Fields

Jira Fields

Jira Project Names (Plan)

Project Names

Previous Article OnePlan & Azure DevOps: Epics - How to Set Up
Next Article OnePlan & Jira: Projects