Jira integration
Overview
Integrating Luna with Jira allows you to import your Jira issues and keep them in sync in Luna bi-directionally. Linking your epics to launches in Luna will 1) give visibility to all stakeholders about upcoming launches and 2) allow you to save hours on reporting, by keeping Jira and Luna in sync.
How can I connect to Jira?
You can connect to Jira on any of the following pages:
Sign up flow
Create a new launch page
Settings >> Integrations page
By clicking on “link” on any of these pages, you will be redirected to the Jira oAuth flow, during which you will consent to the permission scope required by the integration.
The connection between Jira and Luna is a workspace to workspace connection. It’s enough for one user (preferably admin) to connect to Jira, for all users to be able to leverage the connection in Luna.
If Jira doesn’t allow you to proceed with the permission flow, then your IT team will have to whitelist Luna.
Configure your the Jira integration in Luna
In the ‘Settings >> Integrations’ page, click on the Jira box to access all workspace configuration settings. In that page, you can configure Jira for your launches and milestones, separately.
Choose a Jira project
At the workspace level, you can choose the where (Jira project) and in which form (issue type) a launch or milestone can be pushed in Jira.
2-way sync configurations
For each field mapping, you can configure the workspace level syncing settings:
Sync from Jira to Luna only.
Synd from Luna to Jira only.
2-way sync.
Configuration hierarchy
All Jira configurations will cascade in the following order:
Workspace level: any template or launch created will inherit workspace level Jira configurations.
Template level: all launches created using the corresponding template, will inherit the template level Jira configuration.
Launch level: all configurations will be proper to that launch.
Note: New configurations are not applied to activities done previously. They only apply to activities performed after the configurations are set.
How can I import and link issue(s) to launches in Luna?
As a user, you can import any issue that is part of a project, such as: initiative, epic, story, task and bug. We recommend you to import issues which need some level of cross-functional and vertical collaboration and visibility.
Create a new launch from a Jira issue
Click on ‘+ New launch’ → Jira import:
If you import one issue → you will be redirected to the launch detail page (LDP) of the imported issue
If you import more than one issue → you will be redirected to to the All Launches page, which will display the issues you have imported
Link an existing launch to a Jira issue
If you have previously created launches that were not imported from Jira, you can still link this existing launch to a Jira issue.
In the LDP, click on hamburger menu >> Link launch
How can I link Jira issues to a Luna template
While importing issues from Jira, you can link one or more issues to a Luna template. This will allow you to create a more complete and streamlined launch, taking into consideration Jira data complemented with pre-defined modules in the template.
When created, launch data will either come from the Jira issue (data mapping table) or from the template. Some fields clash between the two sources, here’s the import logic:
| Clashing field | Rule |
|---|---|
Summary | The summary section will consist of both the template and the Jira issue summaries. After creation, the summary section will remain in sync with the Jira issue description, whenever a change is made. |
Labels | Labels will be added from both the Jira issue and the template. After creation, labels coming from Jira will sync as per the above mapping. Labels coming from the template will not be impacted. |
Stages | Stages will consist of both template stages and Jira statuses. These stages can be reordered and recategorised into the correct Luna category in Settings >> Stage management |
What launch fields do you import/sync with Jira?
The following fields will get imported in Luna and will stay in sync:
| Luna | Jira issue |
|---|---|
Hamburger menu | Key |
Title | Summary |
Summary | Description |
Owner - If no assignee in Jira, then owner is the person importing the issue | Assignee |
Actual launch date - If no due date in Jira, then launch date is this quarter’s import date | Due Date or Project target date |
Actual start date | Start date or Project start date if not available then Issue creation date |
Prio
| Priority |
Hamburger menu | URL |
Stage | Status |
Labels | Labels |
Label | Fix version |
Label | Sprint |
Label | Goal |
Label | Product area |
How can I import and link issue(s) to milestones in Luna?
As a user, you can link your Jira issues to new or existing Luna milestones.
Create a new milestone from a Jira issue
Create new milestones by importing one or more Jira issues into Luna.
Click on the “Import from Jira” CTA, in the milestones module.
From the Jira importer window, choose the Jira issue to import as milestone.
Link an existing milestone to a Jira issue
Click on the “Link milestone” CTA in the hamburger menu of an existing milestone.
From the Jira importer window, choose the Jira issue to link to the existing milestone.
Milestones data will remain in sync with any changes made to their linked issue, in Jira.
What milestones fields do you import/sync with Jira?
The following fields will get imported in Luna and will stay in sync with the milestones fields:
| Luna - milestones | Jira issues |
|---|---|
Hamburger menu | See details |
Name | Summary |
Owner - If no assignee in Jira, then owner is the person importing the issue | Owner |
Actual Target date | Due Date or Project target date |
Actual start date | Start date or Project start date if not available then Issue creation date |
Stage | Status |
Child issues | List of linked child issues |
How can I push launches and milestones into issues in Jira?
Manual push from Luna to Jira
At the LDP level, you can push the launch or milestone information as an issue in Jira:
Jira configs: define the Jira project and issue type that will be created in Jira.
Click on the ‘Push to Jira’ at the launch or milestone level.
| Push a launch | Push a milestone |
|---|---|
The corresponding issue will be created in Jira and linked with the Luna launch or milestone. Syncing will be performed according to the defined configuration.
Automated push from Luna to Jira
At the template or LDP level, you can define workflows what will automatically push the launch or milestone information as an issue in Jira:
Hamburger menu: click on ‘Set workflows’
Define the milestone, workflow condition and action
When the workflow is executed, the corresponding issue will be created in Jira and linked with the Luna launch or milestone. Syncing will be performed according to the defined configuration.
How can I turn on or off a launch or milestone sync with Jira?
By default, syncing is enabled. In order to stop syncing your launch and milestones with Jira, you will need to opt out from the syncing option available in the LDP hamburger menu:
‘Sync with Jira” enables or disables launch level sync with Jira.
‘Sync milestones” enables or disables milestones sync with Jira.
Last updated
