# About Luna

## Intro to Luna

Luna’s platform helps product and engineering teams ship faster and at a lower cost. We achieve this by focusing on:

* **Progress visibility and goal traceability:** 
  * Luna connects execution data (from Jira, Slack, and other sources) to strategic goals (OKRs).
  * Product and executive leaders can see how each initiative contributes to a Key Result or company Objective, track progress, and spot risks early.
  * Instead of chasing updates, Product and Engineering leaders stay informed about progress, blockers, and changes in real time.
* **Faster alignment with AI:**
  * Luna’s AI turns raw updates, meeting notes, and Jira activity into context and structured insights.
  * PMs and Engineer Managers spend less time writing reports and more time solving problems.
  * Leaders get summaries, risk assessments, and recommended next steps automatically.
* **Cross-functional collaboration:**
  * Launches, approvals, go-to-market work, and other cross-functional efforts are tracked in one place.
  * Luna creates a shared project-level view, bridging the gap between detailed task management tools and leadership reporting needs.

Most teams work in silos, making it hard to see how day-to-day execution connects to company goals. Middle managers spend hours translating Jira updates into reports and slides. Luna replaces this manual work with a shared project-level view, linking roadmaps to OKRs, surfacing risks, and keeping cross-functional teams aligned. 

## Want to see a demo of Luna? 

Reach out to schedule a demo ([calendly](https://calendly.com/paul-withluna/)). We’ll walk through your use cases and show how Luna AI can help.

## Quick setup for your team

Our goal is to minimize “time to value”. When you’re ready, we can schedule an onboarding session to structure your workspace and get you up and running quickly.

## Where does the data come from?

Luna supports three sources of data:

1. **Manual input:** you can use Luna as a standalone tool by entering Objectives, Key Results, Launches, and Milestones directly.
2. **Integrations:** data can be synced from tools like Jira and Slack.
3. **AI-generated insights**: Luna’s AI can analyze meeting notes, Jira activity, or Slack threads and generate structured updates, risks, or summaries.


# Main data fields and structure

The data in Luna is organized around **four main object types: Objectives, Key Results, Launches,** and **Milestones.**

## Hierarchy

Objectives → Key Results → Launches → Milestones

* Objectives are qualitative goals that set the strategic direction.
* Key Results are quantitative goals that measure progress toward an Objective.
* Launches are initiatives that drive Key Results
* Milestones track progress within each launch

{% hint style="info" %}

* One launch can contribute to multiple Key Results, allowing for strategic flexibility.
* Objectives, Key Results, and Launches can be created and used independently. 
* The data below can either be entered directly in Luna, synced from integrations, or enriched by AI.
* You don’t need to adopt the OKR framework to use these fields. If you simply want to track KPIs, you can use the Key Result fields on their own.
  {% endhint %}

## **List of key fields** 

### **Objective level**

<table><thead><tr><th width="180.41015625">Data field</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Title of the strategic objective</td></tr><tr><td>Contributors</td><td>Users or Teams working toward this objective</td></tr><tr><td>Date</td><td>Timeline for achieving the objective</td></tr></tbody></table>

### **KR level**

<table><thead><tr><th width="179.90234375">Data field</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Specific, measurable outcome</td></tr><tr><td>Target date</td><td>When this Key Result should be achieved</td></tr><tr><td>KR score</td><td>Progress score toward the target = <code>((actual - (starting)) / (target - (starting))) * 100</code></td></tr><tr><td>Status</td><td>Current health: On track, At risk, Off track</td></tr><tr><td>Target value</td><td>The goal you're aiming to achieve</td></tr><tr><td>Start value</td><td>Baseline measurement</td></tr><tr><td>Actual value</td><td>Current measured progress</td></tr><tr><td>Owner</td><td>User or Team responsible for this Key Result</td></tr><tr><td>Contributors</td><td>Users or Teams supporting this Key Result</td></tr><tr><td>Linked Launches</td><td>Initiatives driving progress on this Key Result</td></tr><tr><td>External dashboard link</td><td>Link to external tool to track progress</td></tr></tbody></table>

### **Launch level**

<table><thead><tr><th width="180.1875">Data field</th><th>Description</th></tr></thead><tbody><tr><td>Title</td><td>Title of the initiative you want to bring visibility around</td></tr><tr><td>Description </td><td>A high-level description of the initiative to keep everyone informed about its key elements, such as the problem, solution, and potential impact</td></tr><tr><td>Owner</td><td>Point of contact and main driver of the initiative</td></tr><tr><td>Participants</td><td>Users or Teams who are actively collaborating on the initiative or need to stay informed</td></tr><tr><td>Status</td><td><p>- Indicator of the overall health of the initiative: On track, Possible delays, At risk, Paused</p><p>- E.g., changing a status to "At risk" usually triggers a set of email/Slack notifications to the appropriate stakeholders, depending on the company </p></td></tr><tr><td>Stage</td><td><p>- High-level indicator of the phase of the initiative in its lifecycle </p><p>- Examples of stages based on different portions of the lifecycle: </p><p>1- For the GTM: Kickoff, Alpha, Beta, GA</p><p>2- for the entire lifecycle: To be prioritized, Not started, Discovery, Scoping, Implementation, Testing, Launch, Post-launch analysis</p></td></tr><tr><td>Launch and start dates</td><td>Planned and actual start and launch dates of the initiative</td></tr><tr><td>Priority </td><td>Indication of the priority level for your list of initiatives: High, Medium, Low</td></tr><tr><td>Progress score</td><td>Indicator of milestone completion ("Completed milestones" / "Total milestones")</td></tr><tr><td>Link to external source</td><td>Link to external tool (e.g., Jira issue + child issues progress from Jira)</td></tr><tr><td>Labels</td><td><p>- Criteria and attributes for categorizing and organizing your initiatives</p><p>- E.g., these can include metrics (e.g., "Conversion rate"), significant meetings (e.g., "Board meeting"), release names, etc.  </p></td></tr><tr><td>Milestones</td><td>Deliverables and checkpoints within the launch, with owners, approvers, and target dates</td></tr><tr><td>Success metrics</td><td>Outcome-focused measurements to track launch impact, with confidence levels, pre/post shipping values, and link to Key Results for strategic alignment</td></tr><tr><td>Resources</td><td>Documentation, links, and reference materials associated with the launch</td></tr><tr><td>Updates</td><td>Progress updates, status changes, and upcoming priorities</td></tr><tr><td>Risks</td><td>Identified potential blockers, issues, or concerns that could impact launch success</td></tr><tr><td>Decisions</td><td>Key decisions made during the launch process with context and rationale</td></tr></tbody></table>

### **Milestone level**

<table><thead><tr><th width="179.8203125">Data field</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td><p>- Title of the milestone providing clear insights into the work progress</p><p><a href="https://withluna.ai/blog/why-we-focus-on-milestones-not-on-tasks">At Luna, why we focus on milestones, not on tasks - blog post</a></p></td></tr><tr><td>Stage</td><td><p>- High-level indicator of the phase of the milestone in its lifecycle</p><p>- Examples of stages: </p><p>1- Basic level: Not started, In progress, In review, Completed</p><p>2- Can reflect the linked Jira epic status within the list </p></td></tr><tr><td>Target and start dates</td><td>Planned and actual start and target dates of the milestone</td></tr><tr><td>Owner</td><td>Point of contact and main driver of the milestone</td></tr><tr><td>Approvers</td><td>Participants who will need to approve a milestone in due time</td></tr><tr><td>Details</td><td>Behind-the-scenes view of daily work progress in Jira or other tools </td></tr><tr><td>Link to external source</td><td>Link to external tool (e.g., Jira issue + child issues progress from Jira)</td></tr></tbody></table>


# User roles and permissions

## **User roles**

Luna has four user roles with different levels of access and permissions:

* **Admin**: manages the entire workspace.
* **Maker**: edits and collaborates.
* **Member**: read-only access with limited collaboration features (e.g., commenting).
* **Guest**: external user (e.g., external consultant, developer) - read access with limited collaboration features on launches they are invited to.

## **Permissions**&#x20;

### **Workspace level**

<table><thead><tr><th width="239.51171875"></th><th>Admin</th><th>Maker</th><th>Member</th><th>Guest</th></tr></thead><tbody><tr><td>Access to workspace</td><td>✔</td><td>✔</td><td>✔</td><td>✘ - launch per launch basis</td></tr><tr><td>Manage workspace settings</td><td>✔</td><td>Limited</td><td>✘</td><td>✘</td></tr></tbody></table>

### **Goal**

<table><thead><tr><th width="239.80078125"></th><th>Admin</th><th>Maker</th><th>Member</th><th>Guest</th></tr></thead><tbody><tr><td>Create / edit Objectives and Key Results</td><td>✔</td><td>✔</td><td>✔</td><td>✘</td></tr><tr><td>View Objectives and Key Results</td><td>✔</td><td>✔</td><td>✔</td><td>✘</td></tr><tr><td>Be assigned as an OKR owner</td><td>✔</td><td>✔</td><td>✔</td><td>✘</td></tr><tr><td>Contribute to an OKR</td><td>✔</td><td>✔</td><td>✔</td><td>✘</td></tr></tbody></table>

### **Template**

<table><thead><tr><th width="240.44921875"></th><th>Admin</th><th>Maker</th><th>Member</th><th>Guest</th></tr></thead><tbody><tr><td>Create / edit templates</td><td>✔</td><td>✔</td><td>✘</td><td>✘</td></tr><tr><td>View templates</td><td>✔</td><td>✔</td><td>✔</td><td>✘</td></tr></tbody></table>

### **Launch**

<table><thead><tr><th width="240.01953125"></th><th>Admin</th><th>Maker</th><th>Member</th><th>Guest</th></tr></thead><tbody><tr><td>Create / edit launches</td><td>✔</td><td>✔</td><td>✘</td><td>✘</td></tr><tr><td>Edit key launch attributes (stage, status, dates, priority)</td><td>✔</td><td>✔</td><td>✘</td><td>✘</td></tr><tr><td>Add / edit launch components (milestones, success metrics, resources, risks, updates, decisions)</td><td>✔</td><td>✔</td><td>✔</td><td>✘</td></tr><tr><td>View launches information</td><td>✔</td><td>✔</td><td>✔</td><td>✔ - of modules assigned to them</td></tr><tr><td>Be assigned to a milestone (as owner, reviewer)</td><td>✔</td><td>✔</td><td>✘</td><td>✔</td></tr><tr><td>Be assigned to a risk (for mitigation)</td><td>✔</td><td>✔</td><td>✘</td><td>✔</td></tr><tr><td>Configure workflows</td><td>✔</td><td>✔</td><td>✘</td><td>✘</td></tr><tr><td>Comment on launches</td><td>✔</td><td>✔</td><td>✔</td><td>✔</td></tr></tbody></table>

### Roadmap

<table><thead><tr><th width="240.12109375"></th><th>Admin</th><th>Maker</th><th>Member</th><th>Guest</th></tr></thead><tbody><tr><td>Create views</td><td>✔</td><td>✔</td><td>✔</td><td>✘</td></tr><tr><td>Create custom fields</td><td>✔</td><td>✔</td><td>✔</td><td>✘</td></tr><tr><td>Use custom fields for roadmap filtering</td><td>✔</td><td>✔</td><td>✔</td><td>✔</td></tr><tr><td>View existing roadmap views</td><td>✔</td><td>✔</td><td>✔</td><td>✔ - launches they are invited to</td></tr></tbody></table>

### Dashboard

<table><thead><tr><th width="240.4765625"></th><th>Admin</th><th>Maker</th><th>Member</th><th>Guest</th></tr></thead><tbody><tr><td>Create personal dashboard views ("My launches")</td><td>✔</td><td>✔</td><td>✔</td><td>✔</td></tr><tr><td>View dashboard insights</td><td>✔</td><td>✔</td><td>✔</td><td>✔ - launches they are invited to</td></tr></tbody></table>

### Milestone center

<table><thead><tr><th width="240.33203125"></th><th>Admin</th><th>Maker</th><th>Member</th><th>Guest</th></tr></thead><tbody><tr><td>Create milestone views</td><td>✔</td><td>✔</td><td>✘</td><td>✘</td></tr><tr><td>View milestone views</td><td>✔</td><td>✔</td><td>✔</td><td>✔ - launches they are invited to</td></tr></tbody></table>

### AI features

<table><thead><tr><th width="239.88671875"></th><th>Admin</th><th>Maker</th><th>Member</th><th>Guest</th></tr></thead><tbody><tr><td>Turn ideas into plans</td><td>✔</td><td>✔</td><td>✔</td><td>✘</td></tr><tr><td>Generate launch status updates</td><td>✔</td><td>✔</td><td>✔</td><td>✔ - launches they are invited to</td></tr><tr><td>Generate Jira summaries (issues, sprints, fix versions)</td><td>✔</td><td>✔</td><td>✔</td><td>✘</td></tr><tr><td>View AI insights shared by others</td><td>✔</td><td>✔</td><td>✔</td><td>✔</td></tr><tr><td>Access Insights Hub</td><td>✔</td><td>✔</td><td>✔</td><td>✔</td></tr><tr><td>Access All Updates page</td><td>✔</td><td>✔</td><td>✔</td><td>✔</td></tr></tbody></table>

### Slack integration

<table><thead><tr><th width="239.50390625"></th><th>Admin</th><th>Maker</th><th>Member</th><th>Guest</th></tr></thead><tbody><tr><td>Create launches from Slack</td><td>✔</td><td>✔</td><td>✘</td><td>✘</td></tr><tr><td>Edit launches from Slack</td><td>✔</td><td>✔</td><td>✘</td><td>✔</td></tr><tr><td>View launch information from Slack</td><td>✔</td><td>✔</td><td>✔</td><td>✔ - launches they are invited to</td></tr><tr><td>Sync slack with Luna comments</td><td>✔</td><td>✔</td><td>✔</td><td>✘</td></tr></tbody></table>


# Getting started

## Step 1: set up your workspace

**Who**: Admin

* [ ] Click on the sign-up link and follow the onboarding steps
* [ ] Invite users and assign roles (Admin, Maker, Member, Guest) in **Settings > User Management**
* [ ] Create your first teams in **Settings > Team Management**
* [ ] Connect your tools (optional but recommended)  in **Settings > Integrations**

*For more details, see the* [*Workspace settings*](/workspace-settings/team-and-capacity-management) *section*

## Step 2: create your first roadmap

**Who**: Makers or Admins

### Option A: use AI planning

* [ ] **Click "Use AI"** (top left) → "**Turn ideas into plans**"
* [ ] **Describe your goals or initiatives in natural language**
  * Strategic objectives for the quarter
  * Product initiatives you're planning
* [ ] **Review and edit AI suggestions** for OKRs and launches
* [ ] **Import to Luna**
  * Select OKRs to create in Goals
  * Select launches to create and
  * Optionally push issues directly to Jira with linking

*For more details, see the* [*Tell Us Your Plan*](/ai/tell-us-your-plan) *section, and check out our blogpost “*[*Idea to Jira in Minutes: 10x AI Product Planning with TUYP*](https://withluna.ai/blog/ai-product-planning-for-jira)*”*

### Option B: add manually

* [ ] **Create Goals**
  * Go to Goals section
  * Create 1-3 Objectives with measurable Key Results
  * Set target dates and assign owners/contributors

*For more details, see the* [*Goals*](/goals/about-goals) *section*

* [ ] **Create your first launch**
  * Click "**+**" (top left) → **Create launch**
  * Add launch details: name, description, target date
  * Add participants (individuals or teams)

*For more details, see the* [*Launches*](/launches/about-launches) *section*

### Option C: import launches from existing tools

* [ ] **Import from Jira**
  * Click "+" (top left) → Select your tool
  * Choose the project to import issues from
  * Import multiple epics or other issue types as Luna launches
  * Optionally combine with Luna templates

*For more details, see the* [*Create launches*](/launches/create-launches) *section*

## Step 3: explore key features

### Generate your first AI status update

* [ ] **From your launch page**: click "Status Update" (top right)&#x20;
* [ ] **Review AI analysis** in the Insights Hub
* [ ] **Edit and publish** to share with stakeholders

*For more details, see the* [*AI launch status updates*](/ai/luna-launch-status-updates) *section*

### Visit Roadmaps page

* [ ] See your launches in table, timeline, and kanban views
* [ ] Try filtering and custom views

*For more details, see the* [*Roadmap*](/roadmaps/about-roadmaps) *section*

### Check the Milestone Center

* [ ] View all milestones across launches
* [ ] Create team-specific milestone views

*For more details, see the* [*Milestone center*](/milestone-center/about) *section*

### AI Insights Hub

* Access all AI-generated analyses
* Try additional AI features like Jira issues / sprint summaries or external notes ingestion

*For more details, see the* [*Insights Hub*](/ai/about-the-insights-hub) *section*

<br>


# About Goals

## Goals concepts

Luna's Goals feature can be used with or without the formal OKR framework. Teams that don't use OKRs can still leverage Luna's goal-setting and tracking capabilities to align strategy with execution.

At Luna, we structure goals into two levels:

* **Objectives (O):** a qualitative goal. High-level, directional, aspirational
* **Key Results (KR):** a quantitative goal. Specific, measurable outcome that shows progress toward an Objective

{% hint style="success" %}
You can use Key Results as standalone KPIs if you don’t need the full OKR framework.
{% endhint %}

This structure connects strategic intent with measurable progress, regardless of whether you follow formal OKR practices or use your own goal-setting approach.

📚 Some readings from Luna’s blog:

* [Sharing OKRs with other teams: practical strategies](https://withluna.ai/blog/sharing-okrs-with-other-teams-practical-strategies)
* [Actionable OKRs with Jira: guide to traceability and ROI](https://withluna.ai/blog/actionable-okrs-jira)
* [OKRs vs. KPIs: what’s the difference?](https://withluna.ai/blog/okrs-vs-kpis-whats-the-difference)

## Main fields

### **Objective level**

<table><thead><tr><th width="180.41015625">Data field</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Title of the strategic objective</td></tr><tr><td>Contributors</td><td>Users or Teams working toward this objective</td></tr><tr><td>Date</td><td>Timeline for achieving the objective</td></tr></tbody></table>

### **KR level**

<table><thead><tr><th width="179.90234375">Data field</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Specific, measurable outcome</td></tr><tr><td>Target date</td><td>When this Key Result should be achieved</td></tr><tr><td>KR score</td><td>Progress score toward the target = <code>((actual - (starting)) / (target - (starting))) * 100</code></td></tr><tr><td>Status</td><td>Current health: On track, At risk, Off track</td></tr><tr><td>Target value</td><td>The goal you're aiming to achieve</td></tr><tr><td>Start value</td><td>Baseline measurement</td></tr><tr><td>Actual value</td><td>Current measured progress</td></tr><tr><td>Owner</td><td>User or Team responsible for this Key Result</td></tr><tr><td>Contributors</td><td>Users or Teams supporting this Key Result</td></tr><tr><td>Linked Launches</td><td>Initiatives driving progress on this Key Result</td></tr><tr><td>External dashboard link</td><td>Link to external tool to track progress</td></tr></tbody></table>

### <br>


# Create Goals

## AI planning: "Turn ideas into plans"

* Use Luna's AI planning feature to generate goals from your strategic ideas
* The AI suggests both Objectives and Key Results based on your input
* Review and select the generated goals to automatically create them in Luna
* Edit or refine the AI-generated goals as needed

## Create manually

### Objectives

* Required fields: name, target date
* Target date can be set as a specific day, month, or quarter
* Add contributors (individuals or teams) to involve stakeholders

### Key Results

* Required fields: name, target date
* Assign one owner (individual user) and multiple contributors (individuals or teams)
* Add measurable start, target, and actual values

## CSV import

* Click "**+ Upload goals**"
* Follow the CSV format template: [Goal import template](https://docs.google.com/spreadsheets/d/1ZW-HdxEdzmBtfBEqIhPBPmI6K8yIC_N2QxL8fTOt8xc/edit?gid=0#gid=0)
* Upload your file to bulk create goal


# Cascade Goals and link to launches

Luna supports flexible goal hierarchies by allowing you to map goals to parent goals:

* **Objectives** can be mapped to parent Objectives or Key Results
* **Key Results** can be mapped to parent Objectives or Key Results

## How to create goal mapping

1. Open the goal's hamburger menu
2. Select "**Link to OKR**"
3. Choose the parent Objective or Key Result
4. Click "**Link**"

## How to link Key Results to Launches

1. From a Key Result’s hamburger menu, select “**Link launches**”
2. Connect one or more Launches that drive progress toward that KR

This creates traceability from company strategy → team goals → execution<br>

<figure><img src="/files/UJlnCdUZ8ofTaz9vklzr" alt=""><figcaption></figcaption></figure>


# Create goal views

Views let you focus on the goals that matter for your context: by team, quarter, or status.

## Create views

1. Click "+" on the Goals page
2. Apply filters to focus on specific goals:
   * **Status**: filter by goal health (On track, At risk, Off track)
   * **Owner**: filter by goal (O and KR) owners
   * **Contributor**: filter by KR contributors (individuals or teams)
   * **Target date**: filter by date ranges for goal deadlines
3. **Customize columns:** click the **eye icon** to select which columns to display
4. Name your view

## Share views

**Default sharing**: views are shared with all workspace users when created

**Restrict access**:

* Click the arrow next to your view name
* Select "**Share**"
* **Disable** "Share to anyone at Luna"
* Invite specific users to access the view


# Track progress

## Track Key Result progress

* **Update status and values manually:**
  * **Status**: on track, at risk, off track
  * **Values**: start value, actual value, target value
  * **OKR score**: automatically computed ( `(actual - starting) / (target - starting) * 100)`) or manually adjusted (including custom formats like emojis)
* **Link to launches:**
  * Link Key Results to relevant launches using the hamburger menu > "**Link launches**"
  * View high-level status of linked launches to understand how delivery progress impacts Key Result achievement
* **Add the link to an external tracking dashboard** by clicking on the ascending arrow icon next to the hamburger menu

## Key Result details panel

Each Key Result includes a right panel with:

* **Key Resrult metadata**
* **Historical performance**
  * Period-by-period tracking of actual values, target values, and status
  * Percentage change calculations
  * Timeline of progress updates
* **Qualitative updates**
  * Context about why Key Results are on/off track
  * Visible to all users

<figure><img src="/files/blyscysUKJcxwvolLEPg" alt=""><figcaption></figcaption></figure>


# About launches

Luna structures launches around high-level milestones shared across all teams involved in the launch process. Unlike tasks, which measure work, milestones measure progress. Milestones can be linked to resources, updates, risks, and decisions, providing qualitative context on progress.&#x20;

## Launch Details Page (LDP) modules

Each launch contains several key modules:

* **Milestones**: individual deliverables and checkpoints with owners, approvers, and stages
* **Success metrics**: business outcomes that can be linked to Key Results
* **Resources**: documentation, links, and reference materials (including external links)
* **Risks**: identified blockers and mitigation plans
* **Decisions**: key decisions made during the launch process
* **Updates**: progress updates and status reports
* **Participants**: team members and teams involved in the launch
* **Activity**: log of changes, comments, and user interactions (can sync with Slack threads)


# Create launches

## Tell Us Your Plan

Use Luna's AI planning feature to generate launches from your strategic ideas:

1. Describe your objectives and/ or launch concept to the AI
2. AI generates launch name, target date, and maps it to overreaching OKRs
3. Review and refine the AI suggestions
4. Optionally import the launch to Jira with automatic linking

<figure><img src="/files/s4LYGM95IQtg2TDvQPub" alt="" width="285"><figcaption></figcaption></figure>

*For detailed AI planning capabilities, see the dedicated Tell Us Your Plan section in AI*

## Manual creation

<figure><img src="/files/ODbJBNBtD0MyZZFSeRXJ" alt=""><figcaption></figcaption></figure>

### From scratch

1. Click "+" at the top left
2. Define launch date and description
3. Invite participants (individuals or teams)
4. Add milestones, resources, and other modules as needed

### From template

1. Click "+" at the top left
2. Select a predefined template
3. Template automatically applies stages, milestones, participants, and required documents
4. Customize the launch while maintaining template structure

Note: template-based launches have fixed stage sequences that cannot be edited from Launch Details Page. See Templates section in Workspace Settings for more information

{% hint style="info" %}
Template-based launches have fixed stage sequences that cannot be edited from Launch Details Page. See Templates section in Workspace Settings for more information
{% endhint %}

## Import from project management tools

### General import process

1. Click "+" at the top left
2. Select your project management tool (Jira, Asana, ClickUp)
3. Choose the workspace or project to import from
4. Bulk import launches
5. Optionally link imports to Luna templates - this combines tool information with template parameters

<figure><img src="/files/2benYDKn5COqfFzvtYZn" alt="" width="348"><figcaption></figcaption></figure>

*For more details, see the* [*Integrations*](/integrations/jira) *section*

### Jira import with automation rules

For ongoing Jira integration, set up automation rules:

1. Go to Settings > Integrations > Jira
2. Define import rules:
   * Select Jira project and issue type
   * Set conditions (assignee, fix version, sprint, label, date, status)
   * Combine multiple conditions as needed
3. Choose ongoing automation or one-time import
4. Optionally link imports to Luna templates

<figure><img src="/files/8Ijqa4LXe7knCrzcZZ0l" alt=""><figcaption></figcaption></figure>

## Create from Slack

* Ensure Slack is connected (**Settings > Integrations > Slack**)
* Use `/create-launch` command in Slack to create launches from conversations

{% hint style="warning" %}
If your workspace isn't linked to external tools, enable connections in Settings > Integrations.
{% endhint %}


# Manage launches

## From Launch Details Page

From the Launch Details Page, you can edit all high-level launch parameters (owner, participants, stage, status) and work on the various launch modules:

**Launch parameters:**

* Modify name and description
* Update owner, participants, target dates, priority level and labels
* Update launch stage and status
* Edit stages list

{% hint style="warning" %}
You can only edit the list of stages for blank launches (template-based launches or launches imported from project management tools have fixed stages)
{% endhint %}

**Milestone management:**

* **Add milestones**: create from scratch, import from existing milestone list (see [Milestone Management](/workspace-settings/milestone-management) in Settings), or import from task management tools
* **Link milestones to external tools**: connect previously created milestones to Jira issues or other task management systems
* **Check milestone details**: use **hamburger menu > "See details"** to get granular insights into linked milestone progress
* **Assign milestone reviewers**: involve individuals or teams (e.g., marketing, legal) proactively to reduce delays and bottlenecks

<figure><img src="/files/WNzO1RCwiTL85fpWfBXh" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/SMJvHvrdzAKtkeebAMan" alt=""><figcaption></figcaption></figure>

**Other module management:**

* **Define and track success metrics**: link success metrics to Key Results for strategic alignment and track pre and post-launch performance
* **Escalate risks**: collaborate with management on mitigation plans
* **Log key decisions:** document important choices and their rationale
* **Log updates**: track progress and communicate status changes
* **Manage resources**: add documentation, links, and reference materials

<figure><img src="/files/extYyLpZl1CuFjtsR5au" alt=""><figcaption></figcaption></figure>

## From Slack

Use Luna's Slack commands for launch management:

**Creation and editing (Makers only):**

* `/create-new-launch` - create new launches
* `/add-module` - add modules to existing launches

**Access and information (All users):**

* `/get-my-launches` - view summary of your launches
* `/get-launch-module` - get detailed information about specific modules

## From Roadmaps

Edit launches directly from roadmap views for launches you own or participate in: right-click on a launch to edit stage, status, labels, priority, and launch date

<figure><img src="/files/TP8uDcLcKy56FXnMnDXq" alt=""><figcaption></figcaption></figure>

*For more details, see the* [*Roadmap*](/roadmaps/manage-launches-from-roadmaps) *section*

<br>


# Generate status updates

Luna uses AI to create executive-focused status updates that save Product teams time on manual reporting. Our AI analyzes data from Luna, linked Jira issue (if any), and external notes to generate insights about progress, risks, next steps, and business impact.

## Generate updates

### From Launch Details Page

1. Click "Status Update" button at the top of the page

<figure><img src="/files/TXzjSNg4Bol0APjGGkdU" alt=""><figcaption></figcaption></figure>

### From Roadmaps

1. Select one or multiple launches
2. Click "Status Update"

<figure><img src="/files/4KqhCbzod4bPoHXwCswd" alt=""><figcaption></figcaption></figure>

## Edit and publish the update

1. Analysis appears in the Insights Hub
2. Review and act on the update: copy, share, edit, or publish
   * **Share**: User receives an email notification to access the update in their own Insights Hub

<figure><img src="/files/xscch2gqMJeyrCWmHYpE" alt=""><figcaption></figcaption></figure>

**When published, updates appear in:**

* Launch Details Page updates module
* All Updates page
* Launch right panel in Roadmaps
* Slack (if integration enabled)

*For detailed AI capabilities, see the* [*Luna launch status updates*](/ai/luna-launch-status-updates) *section.*


# Subscribe and get notified

## Subscribe to launches and milestones

This feature allows participants **AND** **non-participants** to receive notifications - via the app, Slack, or email - about launches or milestones they want to track:

1. Click the **bell icon** at the top right of Launch Details Page
2. Choose from three notification options:

<figure><img src="/files/AQaNtNtGHXPna3fyJpDq" alt="" width="285"><figcaption></figcaption></figure>

### Option 1: Slack notifications

* Receive notifications when key launch parameters change
* Setup process:
  1. Authorize permission to access the Luna Slack workspace
  2. Choose the Slack channel to receive notifications
  3. Select which notifications to receive:
     * Launch date is updated
     * Launch status is updated
     * Launch stage is updated
     * New milestone is added
     * New weekly update is added
     * New decision is added

<figure><img src="/files/VwSAxjGbabz5CG45xIgb" alt="" width="563"><figcaption></figcaption></figure>

### Option 2: launch subscription

* Subscribe or unsubscribe yourself or others to launch-level notifications
* Example notifications:
* Launch status is changed to "At risk"
* Launch date becomes outdated
* Notification types and channels (in-app, Slack, email) can be modified in **Settings > Notifications**

### Option 3: milestone subscription

1. Subscribe yourself or others to specific milestones
2. Example notifications:
3. Milestone target date becomes outdated
4. Milestone target date is due soon
5. Notification types and channels (in-app, Slack, email) can be modified in **Settings > Notifications**

## Manage subscriptions

Access **Settings > Notifications** to:

* View and manage all your launch and milestone subscriptions
* Configure notification channels and preferences


# About Roadmaps

The Roadmaps page is your central hub for visualizing and managing all launches across your workspace. View launches in multiple formats (table, timeline, kanban), create custom fields for prioritization, and manage launches directly from roadmap views.


# Custom fields

## Create custom fields

Custom fields provide additional data about your launches and can enable prioritization frameworks.

1. Click the **eye icon** at the top of the roadmap table
2. Click "**Create new field**"
3. Configure the field:
   * **Field name** (e.g., "Engineering Effort", "Client Tier", "Revenue Impact")
   * **Field type:** Text, Number, Formula, Rating, Multi-select
   * **For formula fields**: Reference other native or custom fields for calculations
4. Click "Create"

The custom field appears as a new column in the roadmap table.

## Application: use custom fields for prioritization

**Example: RICE score framework**&#x20;

* Create a formula field that calculates prioritization scores: `(Reach * Impact * Confidence Level * 2) / RICE Effort`
* Where Reach, Impact, Confidence Level, and Effort are individual custom fields.

**Benefits:**

* Sort launches by calculated priority scores
* Make data-driven roadmap decisions
* Standardize prioritization across teams
* Track business impact metrics


# Create custom view

## Create custom views

### Create views

1. Click "+" at the right of the roadmap page
2. Apply filters to focus on specific launches
3. Choose display format (table, timeline, kanban)
4. Add dimensions for grouping and organization
5. **Customize columns**: Click the **eye icon** to select which columns to display
6. Name your view

<figure><img src="/files/1IPNwleKm61ZUYYJbfik" alt=""><figcaption></figcaption></figure>


# Share views

**Default sharing**: views are shared with all workspace users when created

**Restrict access**:

* Click the arrow next to your view name
* Select "**Share**"
* **Disable "Share to anyone at Luna"**
* **Invite** specific users to access the view


# Views types

## Table view

* See all launch data in structured columns
* Sort by any field including custom fields
* Use dimensions to create separate swim lanes

## Timeline view

* Visualize launches across time periods (you can choose week/ month/ quarter)
* **Expand milestones**: click the descending arrow next to launch name to show milestones as sub-items
* Access a launch tooltip by hovering over the launch: the tooltip flags key changes and deltas in your launch
* Use dimensions to create separate swim lanes

<figure><img src="/files/ijPl7t6dp6nGStedYPxX" alt=""><figcaption></figcaption></figure>

## Kanban view

* Using dimensions, organize launches by owner, team, stage, status, priority, launch date, key result or outcome
* **Expand milestones**: appear as cards under the main launch card
* Drag and drop for quick status updates

<figure><img src="/files/XXtjJWg4RCgcG8qwN134" alt=""><figcaption></figcaption></figure>


# Manage launches from Roadmaps

Right-click on any launch you own or participate in to edit:

* Stage and status
* Labels and priority
* Start and launch date


# Track progress

## Visual indicators on timeline and kanban

Luna highlights key changes and potential issues:

* **Change indicators:**
  * Status changes (e.g., from On Track to At Risk)
  * Date shifts (e.g., from Aug 2025 to Sep 2025)
  * Stage transitions (e.g., from Implementation to Testing)
* **Number of open risks**
* **Stalling detection:**
  * Launches stuck in the same stage for extended periods (e.g., more than 5 weeks)
  * Status remaining unchanged for long periods (e.g., "At Risk" for several weeks)

**Getting more context**: access the launch right panel for qualitative information about changes and their underlying reasons.

<figure><img src="/files/EelBZPXZycdjvdsIGydD" alt=""><figcaption></figcaption></figure>

## Launch Right Panel

To open the right panel, click the arrow next to any launch name. The right panel contains:

* **Success metrics summary:**
  * Overview of linked Key Results and success metrics
  * Edit success metrics directly: confidence level, pre/post shipping values, KR links
* **Activity and updates:**
  * Published AI-generated status updates
  * Decisions, risks and updates from launch modules

<figure><img src="/files/899fUgewFx9bnRLyRLIT" alt=""><figcaption></figcaption></figure>

## Launch status updates

Generate AI-powered status updates for one or multiple launches:

1. Select one or multiple launches from roadmap views
2. Click "**Status Update**"
3. AI generates comprehensive status update covering all selected launches
4. Review, edit, and publish through the Insights Hub

<figure><img src="/files/WTctUQMZhHQfCtWGVzVA" alt=""><figcaption></figcaption></figure>

*For detailed status update capabilities, see the* [*AI*](/ai/luna-launch-status-updates) *section.*

This centralized management approach enables efficient oversight of your entire product portfolio while maintaining the flexibility to drill down into specific launch details when needed.<br>


# About the Insights Hub

The AI insights hub is your centralized location for all AI-generated analyses and outputs. Access it from the left menu under "AI insights hub" to view, manage, and act on AI-generated insights.

<figure><img src="/files/iD3pwPBeDRN21R5SRgge" alt="" width="375"><figcaption></figcaption></figure>


# Tell Us Your Plan

This feature allows you to transform your ideas into executable plans using Luna's AI planning capabilities.

## What it does

Tell Luna about your goals, and initiatives through natural language input. You can also provide meeting notes, PRDs, or user stories you want to create. Luna's AI automatically generates:

* **OKRs** with objectives and measurable key results
* **Roadmaps** with structured initiatives
* **Jira issues** ready for development execution including user stories with detailed descriptions and acceptance criteria

## Value and benefits

* **Save significant time** structuring and translating ideas into executable plans
* **Bridge strategy to execution** by connecting high-level goals to specific tasks
* **Kick off execution immediately** through automatic import to Jira

## How to use Tell Us Your Plan

1. Click "**Use AI**" (top left)
2. Select "**Turn ideas into plans**"
3. Input your ideas, goals, meeting notes, or user stories
4. Review AI-generated suggestions
5. (if needed) **Refine and iterate**: click on “Refine input” to edit your input and rerun the analysis for better results
6. **Import to Luna**
   * Import OKRs to Luna Goals
   * Import initiatives to Luna Launches (optionally push to Jira with automatic linking)
   * (optional) Combine with Luna templates when importing
7. **Push issues directly to Jira**
   * Choose the project and issue type destination in Jira
   * (optional) Select a sprint and/ or a fix version
   * (optional) Map to an existing parent issue

<figure><img src="/files/ga0PyXycweqU35KhFZ2E" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/SUp2oMxx0UYfRgm58qv2" alt="" width="563"><figcaption></figcaption></figure>


# AI ingestion of external notes

This feature allows you to extract strategic insights from meeting notes and external content to keep launches up-to-date.

## What it extracts

Luna's AI analyzes your notes to identify:

* **Projects/ launches** mentioned
* **User and teams mentions**
* **Risks** and their current status
* **Decisions** (taken and pending)
* **Updates** on progress and priorities
* **Next steps** and **action items**

## How to use external notes analysis

1. Click "**Use AI**" (top left)
2. Select "**Enrich with Notes and Slack**"
3. Copy-paste your notes
4. Click "**Submit**"

## Context enhancement

If the AI needs clarification, it displays questions in the "**Context & Enrichment**" module - examples:

* Clarify which launch is being discussed
* Identify mentioned users vs Luna workspace users

After providing additional context, reprocess the analysis to incorporate the enhanced information.

## Managing historical notes

* You can view all previously ingested notes in the “History tab” of the ingestion module

{% hint style="warning" %}
Deleting notes from history removes the analyzed content from Luna's database - the information will not be used anymore for status updates
{% endhint %}

## Integration with status updates

Extracted information integrates with Luna's status update generation, using RAG (Retrieval-Augmented Generation) to provide comprehensive launch insights.

<br>


# Jira issues, sprint, fix version summaries

This feature allows you to g generate AI insights from your Jira data to understand development progress and identify optimization opportunities.

## How to generate Jira summaries

1. Click "**Use AI**" (top left)
2. Select "**Summarize Jira insights**"
3. Choose analysis type:
   1. **Jira issues summary:**
      1. Analyze progress on one or multiple issues
      2. Assess potential blockers and timeline impact
      3. Generate actionable recommendations
   2. **Sprint summary:**
      1. Analyze completed work and potential blockers
      2. Get actionable recommendations to minimize spillovers
      3. For completed sprints: retrospective of successes and improvement areas
   3. **Fix version summary:**
      1. Analyze completion status and potential blockers
      2. Get actionable recommendations to minimize delays
      3. For completed releases: retrospective analysis

## Data points and insights

Luna's AI analyzes a variety of data points including:

<table><thead><tr><th width="191.34765625">Analysis type</th><th>Description</th></tr></thead><tbody><tr><td>Issues completion</td><td>Done vs remaining work by effort and priority level</td></tr><tr><td>Scope creep</td><td>Track scope increases after work begins by monitoring child issue additions, description expansions, and reopened issues</td></tr><tr><td>Blockers</td><td>Analyze comments to identify blockers and resolution status</td></tr><tr><td>Dependencies</td><td>Identify dependencies that are at risk of causing delays</td></tr><tr><td>Timeline risks</td><td>Overdue issues and stalling issues that haven't progressed</td></tr><tr><td>Velocity</td><td>Calculate spillover risks for sprints and delay risks for fix versions/issues</td></tr><tr><td>Workload</td><td>Assess workload allocation and team imbalances</td></tr></tbody></table>

## Follow-up actions

After generating Jira summaries, convert insights to action:

* Click on **Follow-ups: Import issues as launches**
* Luna will recommend issues to import and track as launches in Luna.
* **Import to Luna**: select relevant Jira issues and import them as Luna launches
* Maintain automatic linking between Jira and Luna for ongoing synchronization

<figure><img src="/files/WBICIDz47WjiBNDiDOTA" alt=""><figcaption></figcaption></figure>

<br>


# Luna Launch status updates

Luna's AI generates executive-focused launch status updates that save Product Managers time by creating comprehensive reports with insights from multiple data sources.

## How it works

Luna's AI synthesizes information from: **Luna data**, **Jira data** and **external notes.**

1. **Luna data:**

<table><thead><tr><th width="181.3203125">Category</th><th>Data points</th></tr></thead><tbody><tr><td>Launch metadata</td><td>Dates (start, end), stage, status, priority, owner, description, custom fields</td></tr><tr><td>Business Impact</td><td>Linked KR, outcomes</td></tr><tr><td>Progress &#x26; timeline</td><td>Milestone completed / due in next 7 days, last 7 days updates, last 7 days decisions</td></tr><tr><td>Blockers</td><td>All open risks and their current status</td></tr></tbody></table>

2. **Jira data**: when launches are linked to Jira issues, AI performs the comprehensive Jira analysis detailed above and combines the output with Luna data and external notes data.
3. **External notes integration:** extracts updates, risks, decisions, and next steps from past 7 days of notes using RAG - *more info on ingestion* [*here*](/ai/ai-ingestion-of-external-notes)*.*

## Structure and content

Status updates include:

* **Executive summary**: high-level status and business impact assessment
* **Progress and timeline**: milestone completions, achievements, and recent decisions
* **Risks and blockers:** open risks from the different sources
* **Next steps**: upcoming milestones, priorities, and recommended actions

## Status inference

Based on all collected data signals, Luna's AI infers an overall launch status (On Track, At Risk, Possible Delays) using predefined rules that analyze the comprehensive data points. This AI-inferred status may differ from the manually set status in Luna, providing an objective assessment based on actual progress indicators and identified blockers.

## How to generate status updates

* **From Launch Details Page:**
  * Click "**Status Update**" button at the top right
* **From Roadmaps:**
  * Select one or multiple launches
  * Click "**Status Update**"

## Review and publish process

1. Analysis appears in the [**AI Insights Hub**](/ai/about-the-insights-hub)
2. Review, edit, copy, or share the generated update
3. **Share functionality**: recipients receive email notifications to access the update in their own Insights Hub.
4. **Publish** to distribute across:
   * Launch Details Page updates module
   * All Updates page
   * Launch right panel in Roadmaps
   * Slack (if integration enabled)

<figure><img src="/files/ZIcgxtwn2jSe7rC3ISqv" alt=""><figcaption></figcaption></figure>


# About

The All Updates page centralizes status updates across all launches in your workspace, eliminating the need to check individual launches for their latest updates.

## What updates appear here

* [**AI status updates**](/ai/luna-launch-status-updates) that have been published
* **Updates** added in the Update module in Launch Details Pages

## Filtering and organization

* **Time-based organization**: updates organized chronologically by publication date
* **Status-based filtering**: view only updates that are "At Risk"
* **Time-based filtering:** view only past x days updates
* **Team-based filtering**: view only:
  * AI updates published by a user whose primary team is the selected team at the time the update was published
  * Updates from LDP where the launch team equals the selected team
* **Launch-specific filtering** (stage, status, date): focus on updates from specific launches

## Use cases

* **Executive oversight**: quick portfolio health check across all initiatives
* **Risk monitoring**: identify all launches requiring attention through status-based filtering
* **Team coordination**: stay informed about updates from other teams' launches

The All Updates page serves as your central command center for understanding the health and progress of your entire product portfolio at a glance.

<figure><img src="/files/eydPOVYsEEThmk0miopQ" alt=""><figcaption></figcaption></figure>

<br>


# About

The Milestone Center allows teams to view and manage milestones across all launches in a centralized kanban interface. Instead of navigating to individual launches, users can see milestones from all public launches, manage approvals, and track progress workspace-wide.

**Key benefits**

* **Cross-launch visibility**: view milestones from all public launches, not just your assigned ones
* **Centralized approvals**: approvers can approve or decline milestones without accessing individual launches
* **Team coordination**: create team-specific views for pending approvals
* **Efficient milestone management:** edit details and move milestones between stages and dates using drag-and-drop

<figure><img src="/files/ZxPvyHVDaNZTfSpLmO3u" alt=""><figcaption></figcaption></figure>


# Create custom views

## Create views

1. Click "**+**" to create a new milestone view
2. Name your view
3. Apply filters to focus on specific milestones
4. Choose organization method (stage, owner, target date, team)

## View management options

* **Hide views:** remove views from your interface without deleting
* **Share views**: restrict access to specific users or teams instead of company-wide visibility


# Filter and organize

## Available filters

<table data-header-hidden><thead><tr><th width="201.67578125"></th><th></th></tr></thead><tbody><tr><td>Launch stage</td><td>Filter by the parent launch's current stage</td></tr><tr><td>Milestone stage</td><td>Filter by milestone progress (Not Started, In Progress, In Review, Completed ..)</td></tr><tr><td>Milestone owner</td><td>View milestones assigned to specific users</td></tr><tr><td>Milestone approver</td><td>Focus on milestones requiring approval from specific users</td></tr><tr><td>Team</td><td>Filter by team assignment (milestone owner or approver teams)</td></tr><tr><td>Milestone target date</td><td>Filter by due dates and deadlines</td></tr></tbody></table>

## Organization methods

* **By stage**: group milestones by their current stage
* **By owner**: organize by who's responsible for each milestone
* **By target date**: sort by upcoming deadlines
* **By team**: group by team assignments


# Manage milestones

* **For approvers: approve or decline** milestones directly from the kanban interface
* **For eligible users (launch participants): edit milestone details** (stage, target date, owner, approver) by right clicking on the milestone or via drag and drop


# Use cases

1. **Review queues**: create team-specific views to manage approval workflows (e.g., Marketing review queue, Legal review queue)
2. **Status boards**: organize milestone visibility by team needs:
   1. **Team workload views**: see all milestones assigned to specific teams
   2. **Deadline tracking:** focus on upcoming milestone due dates
   3. **Cross-team dependencies**: identify milestones affecting multiple teams
3. **Workflow management**
   1. **Pending approvals**: quick access to milestones requiring your approval
   2. **Team capacity**: understand milestone distribution across team members
   3. **Progress tracking:** monitor milestone completion across all launches

<figure><img src="/files/ZxPvyHVDaNZTfSpLmO3u" alt=""><figcaption></figcaption></figure>


# Team and Capacity management

## Team overview

Teams in Luna provide a flexible way to organize users, filter content, and coordinate work across your workspace.

**Key benefits**

* **Focus**: filter OKRs, launches and milestones by team
* **Scalability**: organize large workspaces without losing visibility
* **Ownership**: assign teams to OKRs, launches, and milestones (directly or through templates)

**Team structure**

* Users can join multiple teams
* Each user has a **primary** team for filtering and organization
* First team joined becomes the primary team by default
* Users can change their primary team at any time

**Access & visibility**

* Users can see all launches regardless of team (existing permissions apply)
* Team membership doesn't override existing user role permissions (Admin/Maker/Member/Guest)

### Create and manage Teams

**Create a Team**

1. Go to **Settings > Team Management**
2. Click "**+ Create new team**"
3. Fill in the team details:
   * Team name (required)
   * Team description
   * Team picture (optional)
   * Add initial team members

**Manage Teams**

In **Settings > Team Management**, you can:

* View all workspace teams
* See which teams you've joined
* Set a team as your primary’s team
* Edit team details (name, description, picture, capacity and workload)
  * More info on Capacity management [below](#capacity-management)
* Add or remove team members
* Delete teams (if you have permissions)

### Join a Team

**During signup**

1. You'll see available teams during the signup process
2. Select the teams you want to join
3. **The first team you select becomes your primary team automatically**

**After signup**

1. Go to **Settings > Team Management**
2. Browse the list of available teams
3. Click on a team to view details
4. Click "**Join team**" to become a member

{% hint style="info" %}
Admins and Makers can also add you to teams directly.
{% endhint %}

### Define your primary Team

Your primary team is used for filtering and organizing your work across Luna.

**To set or change your primary team**

1. Go to Settings > Team Management
2. Find a team you're already a member of
3. Click the menu icon (⋯) next to the team name
4. Select "Set as primary"

**What your primary team affects**

* Default filtering in roadmap views → filtering on a certain team will display launches where any participant's primary team is this team
* Team-based organization in Timeline → setting Teams as dimension will categorise launches based on participants' primary teams
* Team-based organization in Kanban boards → setting Teams as dimension will categorise launches based on the owner's primary team

### Leave a Team

1. Go to **Settings > Team Management**
2. Find the team you want to leave
3. Click the menu icon (⋯) next to the team name
4. Select "**Leave team**"

{% hint style="warning" %}
You cannot leave your primary team without first setting a different primary team
{% endhint %}

{% hint style="warning" %}
If you're the last member of a team, consider transferring ownership or deleting the team instead
{% endhint %}

### How Teams are used across Luna

**In Launch management**

* **Assigning teams to launches**
  * Add teams as launch participants when creating launches
  * Assign teams as milestone owners or approvers
  * Note: When you assign a team, all individual team members also become available for selection
* **Team inheritance from templates**
  * Templates can include default team assignments
  * When creating a launch from a template, team assignments are automatically applied

**In filtering and views**

* **Roadmap filtering**
  * In Roadmap views (Table/Timeline/Kanban), filter by one or more teams → Shows launches owned by team members whose selected team is their primary team
  * Add "Team" as a dimension in Timeline view to group launches by all participants' primary teams
  * In Kanban view, columns are organized by team names based on owner's primary team

**In OKRs**

* Assign teams as Objective contributors
* Assign teams as Key Result owners or contributors

## Capacity management

### **Capacity configuration**

Before setting team capacity, configure your workspace units:

**Capacity units**

* **Weeks**: measure capacity in time periods
* **Points**: measure capacity in story points or effort units

**Workload units**

* **Points**: direct point assignments
* **T-shirt sizes**: use size estimates (S/M/L/XL) with custom point mapping

**T-shirt size mapping**: define point values for each size (example):

* S = 20 points
* M = 40 points
* L = 80 points
* XL = 160 points
* ..

<figure><img src="/files/cPrDtMxeEAvLX6JGxMNt" alt=""><figcaption></figcaption></figure>

### **Set team capacity**

1. Go to **Settings > Team Management**
2. Click on a team name to open team details
3. For each team member, set their individual capacity within this team:
4. Enter capacity directly, or
   1. Use the breakdown method (Starting capacity, then adjust for Bugs % and Holidays %)
   2. Enter current workload for each team member
5. **Team totals are automatically calculated** by summing individual member values
6. Subscription percentage is automatically computed (Team Workload ÷ Team Capacity)

<figure><img src="/files/WHGJjWM3kCLMrENqXjea" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Users define their capacity within their **primary team**. If someone belongs to multiple teams, their capacity is set in their primary team context.
{% endhint %}

### **Understanding capacity metrics**

**Individual level**

* Capacity: available bandwidth for each team member (in your configured units)
* Workload: current work assigned to each team member (manually entered)
* Subscription percentage: automatically calculated utilization (Individual Workload ÷ Individual Capacity)

**Team level**

* Team capacity: sum of all individual member capacities
* Team workload: sum of all individual member workloads
* Subscription percentage: automatically calculated team utilization (Team Workload ÷ Team Capacity)

### **Using capacity data**

**Use capacity metrics to**

* Identify over-subscribed teams before planning new launches
* Balance workload distribution across teams
* Make informed decisions about launch prioritization
* Plan resource allocation for upcoming quarters


# Milestone management

## Create predefined milestones

Predefine a list of milestone templates with their corresponding owners and approvers. This creates a reusable library of standard milestones that can be used across launches and templates.

{% hint style="info" %}
All predefined milestones are available to all users in the workspace
{% endhint %}

1. Go to **Settings > Milestone Management**
2. Click "**Add a new milestone**"
3. Enter milestone details:
   1. Name (required)
   2. Owner (individual user or team)
   3. Approvers (individual users or teams, if relevant)

## Use predefined milestones

Your predefined milestone library can be used when creating milestones in:

* **Stage Management**: When adding milestones under specific stages
* **Launch Details**: When creating milestones directly in a launch
* **Templates**: When setting up milestone templates for reuse

**How it works**: when creating a milestone, click the arrow next to "Add new milestone" and select "+ Import from existing list" to choose from your predefined milestones. This ensures consistency and saves time on repetitive milestone setup.

<figure><img src="/files/eu7uivSxltpqb5akSjUc" alt=""><figcaption></figcaption></figure>


# Stage management

## What are stages

Stages are high-level phases that track the lifecycle of launches and milestones. Unlike milestones (which are specific deliverables), stages represent broad phases of work like "Discovery", "Implementation", or "Launch".

**Key differences**

* **Stages**: high-level phases (Discovery, Implementation, Launch)
* **Milestones**: specific deliverables within those phases (PRD complete, Beta testing done)

Luna supports separate stage systems for launches and milestones, each with their own categories and workflows.

## Stage categories

**Launch stage categories**

* **Backlog**: launches requested and added to the backlog
* **Not Started**: planned launches not yet started
* **In Progress:** active launches being worked on
* **Completed:** launched features (won't be marked overdue, excluded from in-progress reports)
* **Closed**: cancelled or discontinued launches

**Milestone stage categories**

* **Not Started**: milestones not yet begun
* **In Progress:** milestones actively being worked on
* **In Review**: milestones requiring approver attention (triggers pending action notifications)
* **Completed**: finished milestones

## Default stages

Luna provides predefined stages when you create a new workspace, with some stages being editable and others fixed:

**Launch stages**

* **Examples of editable stages:** To be prioritized, Discovery & planning, Setup essentials, Development, Enablement, Beta, Post launch implementation ..
* **Non-editable stages**: Not started, Kickoff, Planning & scoping, Implementation, Marketing readiness, Launched

**Milestone stages (non-editable):** Not started, In progress, In review, Completed

## Create and manage stages

### Create new stages

1. Go to **Settings > Stage Management**
2. Click "**+ Create new stage**"
3. Enter stage name
4. Select or drag the stage into the appropriate category
5. Save the stage

### Order stages

* **Drag and drop** stages within categories or between categories

### Edit and delete stages

* Edit stage names and categories anytime
* Delete custom stages (some default stages cannot be deleted)

{% hint style="warning" %}
If you delete a stage that has launches using it, those launches will need new stage assignments
{% endhint %}

## Template stages

### Set up template stages

1. When creating or editing a template, define the stage sequence
2. Template stages determine what stages are available for launches created from this template
3. Users creating launches from templates inherit the predefined stage flow

### Blank template stages

* Launches created "from scratch" use the "blank template" stage configuration
* Configure blank template stages in **Settings > Stage Management**
* This sets the default stage options for ad-hoc launch creation

## Predefine milestones under stages

From Stage Management, you can predefine standard milestones for each stage:

**Example:**

* Stage: "Marketing Readiness"
* Predefined milestones: Landing page copy, Email campaign, Social media assets

### Set up predefined milestones

1. In **Settings > Stage Management**, click on a stage
2. Add standard milestones that should appear whenever this stage is used
3. When users create launches (via template or blank), these milestones are automatically added
4. Users can edit, delete, or add more milestones as needed

## Update stages in Launch Details Page

* **Blank launches** (created from scratch): users can change the list of stages freely in the launch details page
* ⚠️ **Template launches:** stages are fixed based on the template and cannot be edited in launch details

### **Stage change impacts**

* **Removing a stage**: if you remove a stage that has milestones, those milestones move to an "Other milestones" section (uncategorized)
* **Stage requirements**: every launch must have at least one "Not Started" and one "Completed" stage available

## Stage-based workflows and automation

### Workflows

* Stages can trigger custom workflows that you define e.g., “When milestone reaches "In Progress" stage → Create a Jira epic”
* Configure workflows using the hamburger menu of the launch or milestone in the Launch Details Page and selecting "Set workflows".

### Notifications

Stage changes can trigger notifications that you enable in **Settings > Notifications** (examples: receive a notification when “Launch stage is changed”, “Milestone stage is part of the 'Completed' category” ..)

### Built-in stage behaviors

Some stage behaviors are automatic:

* Launches in "Completed" category are excluded from overdue tracking and progress reports
* Milestones in "Completed" category are excluded from overdue tracking and progress reports
* Milestones in "In Review" stage create pending actions and notifications for approvers

## Stage management best practices

**Launch stages should reflect your workflow:**

* Map stages to actual phases your team follows
* Use consistent naming across templates
* Align stages with team responsibilities

**Use stage categories strategically:**

* "Completed" category affects reporting and overdue tracking
* "In Review" category creates pending actions for approvers
* Stage categories drive Luna's automated workflows

**Template organization:**

* Create templates with logical stage sequences
* Use predefined milestones to standardize deliverables
* Configure blank template stages for ad-hoc launches


# Label management

Labels help categorize and organize your launches across the workspace. Use labels to tag launches by project type, priority, team focus, or any other criteria that helps with filtering and organization.

Any Maker can create, edit, or delete labels workspace-wide.

## Create labels

### Create manually

In **Settings > Labels Management**

1. Go to **Settings > Labels Management**
2. Click "**Add new label**"
3. Enter:
   1. Label name (required)
   2. Color for visual identification

**Create labels on-the-go**

* **From launch pages**: create labels while editing launch details
* **From template pages**: create labels while setting up templates
* Labels created anywhere automatically appear in the Labels Management list

### Labels created automatically

Luna automatically creates labels in certain situations:

* **From Jira imports:** when importing launches from Jira, existing Jira labels are automatically added to your Luna labels list
* **From "Tell Us Your Plan"**: when using AI planning, Luna automatically creates a label like "Your plan - 14 Aug 2025" to group related launches from that planning session

## Use labels

### **Add labels to launches**

* Add labels to launches for categorization and organization
* Labels help identify launch types, priorities, or themes at a glance
* No limit on labels per launch

### **Filtering and views**

* In Roadmap views: filter launches by one or more labels
* In Timeline views: use labels as dimensions to group and organize your roadmap


# Templates

Templates allow you to standardize launch processes by predefining stages, milestones, participants, and required documentation. This ensures consistency and saves time when creating similar launches.

## View templates

View all workspace templates in Settings > Templates with options to:

* **Edit**: click hamburger menu next to template name > Edit (template owner only)
* **Copy**: duplicate existing templates to create variations (template owner only)
* **Create new**: click "Create new template" button (Admins and Makers)

## Create a new template

1. Click "**Create new template**" button
2. **Template basics:**
   * Template name (required)
   * Short description with talking points for users (e.g., "What problem are you solving?", "What users are impacted?", "What are the KPIs?") (required)
3. **Template configuration:**
   * **Add labels:** categorize your template for easy identification
   * **Define stages and milestones**: outline the project workflow
   * **Add participants**: could be teams and/or individuals
   * **Set milestone owners/approvers**: assign teams or individuals to milestones
   * **Required resources:** specify documents needed (e.g., Figma mocks, PRD)
4. Save the template

{% hint style="warning" %}
To add stages to your template, ensure they are created in **Stage Management** first.
{% endhint %}

### Adding teams as participants

* Teams can be assigned as default launch participants
* When assigning milestone owners/approvers, all members of assigned teams become available as individual options

## Use templates

During launch creation, select a template to automatically apply:

* Predefined stages and milestones
* Default participants and team assignments
* Required document placeholders
* Standard milestone owners/approvers

Launches created from templates can be modified:

* **Can modify**: labels, milestones, participants, documentation, milestone assignments
* **Cannot modify:** stage sequence (locked to template structure)

## Update a template

When you update a template:

* Changes only apply to future launches using the template
* Existing launches created from the template remain unchanged
* No retroactive updates to previous launches


# Billing

## Pricing and plans&#x20;

Please visit [our website](https://withluna.ai/pricing) for more information about our current plans, pricing and list of features.&#x20;

## How does our billing work

At Luna, we follow a “fair billing” policy: you are only charged for the Makers in your workspace. We will not require you to pre-purchase a bulk package of Makers.

* Makers (including admins) are paid users.&#x20;
* Members are always free.

Note that only Makers who accept the invitation to join your workspace will be billed.&#x20;

[More info about the different types of users](/luna-101/user-roles-and-permissions)

Billing frequency options:&#x20;

* Monthly: your workspace will be billed monthly, on the 1st of each month. Your first invoice will be prorated for the remaining days until your next billing cycle
* Yearly: your workspace will be billed annually, starting from the subscription date

## Manage your billing&#x20;

All billing management features and information are available in the Customer Portal, accessible by navigating to the **Settings > Billing** page. From there, you can:

* View and change your plan
* Access your personal billing information
* View and update your payment details&#x20;
* View your invoices

## How can I add or remove Makers from my plan &#x20;

Navigate to **Settings > User management** to add or remove Makers from your plan. Please note that the Free plan has a limit of 3 Makers.

Your billing will be impacted as follows:&#x20;

* Monthly cycle: an invoice will be issued at the start of the new billing period, including pro-rata charges for any newly added Makers&#x20;
* Yearly cycle: pro-rata charges for the remainder of the year will be applied, and billed on the 1st of the following month

## How can I upgrade or downgrade my plan

Navigate to **Settings > User management** and select the new plan. You will be directed to the customer portal to complete this action. Note that downgrading from Launch to Free plan will result in feature restrictions according to the Free plan.

Your billing will be impacted as follows:&#x20;

**Changing from Free to Launch plan:**&#x20;

* Monthly cycle: your workspace will be billed monthly, on the 1st of each month. Your first invoice will be prorated for the remaining days until your next billing cycle.
* Yearly: your workspace will be billed annually, starting from the subscription date.

**Changing from Launch to Free plan:**

* Monthly cycle: your new plan will take effect at the start of the next billing month.
* Yearly cycle: mid-cycle downgrades are not supported. If you're unsure about committing to a full year, we recommend starting with a monthly plan first.


# Jira

## 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.

{% hint style="info" %}
If Jira doesn’t allow you to proceed with the permission flow, then your IT team will have to whitelist Luna.
{% endhint %}

## Configure your 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.

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXfdaUfRiLil1f82OIS78s4R18oW6vy2rWHYkDksD4LZ-OJSUSSU_6D1YZcLu0gM-WNO20VhWS_4IW1rmVyThpu2J7OtTCI5D0Kb29JtCqoL_kZZjv3uhG0Hr8z5YdN8q1YtLvEg2QsJShRbaRQZBr9k5Yyu?key=vFToHcRzl46s99fckfz_GA" alt=""><figcaption></figcaption></figure>

### 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.&#x20;

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXe9IJKWpqXqPtFKpJz2pV99nIAsw-JB5UIOIgu7eXlAASBNKqnOHmFQEzeYjw8dpsjjjbn0W92gFlsT0RHUZRoRR9yeRPTiw5SnX71MiezjRSAPBeJ_2-kcMBLzEUlDA7cEfZ2MxNtmsYesRSRumhNxszad?key=vFToHcRzl46s99fckfz_GA" alt=""><figcaption></figcaption></figure>

### 2-way sync configurations

For each field mapping, you can configure the workspace level syncing settings:&#x20;

1. Sync from Jira to Luna only
2. Synd from Luna to Jira only
3. 2-way sync

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXdtnsA7wiNZyfjd_uSQOKLIZVAE041_uRscsMTkNy-0TYIUUh1Si2f-W8OoBRDGo9PBxS-N0R6fQW4YurTO23rl2PlsZN4oRLwWuYz6SMTyte23itLlm-mPZvVUM91OeL2ICdMC8jTmay9Ws3AiLvtWX-yY?key=vFToHcRzl46s99fckfz_GA" alt="" width="563"><figcaption></figcaption></figure>

### Configuration hierarchy&#x20;

All Jira configurations will cascade in the following order:&#x20;

1. **Workspace level**: any template or launch created will inherit workspace level Jira configurations
2. **Template level**: all launches created using the corresponding template, will inherit the template level Jira configuration
3. **Launch level**: all configurations will be proper to that launch

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXf_J9fWmP44H_x_0DMrdNGf5pQYKJ4PLCHAeUzZaBYw1Vfq5Rwgcc9lFAMst1YVcZ-RmbySPZaFOtGqZ1bG9XipHCsIA3M_HPU_HDAiHUCTPPxtgGzhk4cTHR67zsDvSmmTfC23HFp8h0ABDNZ4K9HVRiRZ?key=vFToHcRzl46s99fckfz_GA" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="info" %}
New configurations are not applied to activities done previously. They only apply to activities performed after the configurations are set.
{% endhint %}

## 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.&#x20;

### Create a new launch from a Jira issue &#x20;

Click on ‘**+**’ → Jira import:&#x20;

* 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&#x20;

### Link an existing launch to a Jira issue &#x20;

If you have previously created launches that were not imported from Jira, you can still link this existing launch to a Jira issue.&#x20;

In the LDP, click on **hamburger menu > Link launch**&#x20;

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXc4dgbUzW0dJrwubfBPMSbSHyNOzrLxQOH2FWNqaZm3qkiEjMc8pLO4zkShzFYgwa9wpNVWyf62DZK8kTsHGQo1kxUS68OGAqyNCyhh_c0bX197PHPIXuDvWTF6sUdYhPE1HU6_yLOHDZZh60t1PX-acBOh?key=vFToHcRzl46s99fckfz_GA" alt="" width="188"><figcaption></figcaption></figure>

## How can I link Jira issues to a Luna template &#x20;

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.&#x20;

When created, launch data will either come from the Jira issue ([data mapping table](https://docs.google.com/document/d/1M_uWd2Sh28gOrnpF8DKgVvD47yFflNSH8hQEx_kGqqs/edit#heading=h.qnhuo0hq31nh)) or from the template. Some fields clash between the two sources, here’s the import logic:&#x20;

<table><thead><tr><th width="139.87890625">Clashing field</th><th>Rule</th></tr></thead><tbody><tr><td>Summary</td><td><p>The summary section will consist of both the template and the Jira issue summaries. </p><p>After creation, the summary section will remain in sync with the Jira issue description, whenever a change is made. </p></td></tr><tr><td>Labels</td><td><p>Labels will be added from both the Jira issue and the template. </p><p>After creation, labels coming from Jira will sync as per the above mapping. Labels coming from the template will not be impacted.</p></td></tr><tr><td>Stages</td><td>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</td></tr></tbody></table>

## 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                                                                              |
| <p>Owner</p><p>- If no assignee in Jira, then owner is the person importing the issue</p>                 | Assignee                                                                                 |
| <p>Actual launch date</p><p>- If no due date in Jira, then launch date is this quarter’s import date </p> | Due Date or Project target date                                                          |
| Actual start date                                                                                         | <p>Start date or Project start date<br><br>if not available then Issue creation date</p> |
| <p>Prio</p><ul><li>Low = Lowest, Low</li><li>Medium = Medium</li><li>High = Highest, High</li></ul>       | 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.&#x20;

### Create a new milestone from a Jira issue&#x20;

1. Create new milestones by importing one or more Jira issues into Luna
2. Click on the “Import from Jira” CTA, in the milestones module
3. From the Jira importer window, choose the Jira issue to import as milestone

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXdIuDo2DRoKj9BFU4QJiux6iSmZCudqhI1T9Ofa6jPMnfl9D7WzRqEOwOYAtBpAmjhj_iNRQpH5ivCfXO5K5FWlNUUiLufnsuRhxvn-HbCu_YluYmV7Wf3Gy-UFRbe2e4CdnXvcLAdES-TyxoUk1J5Yjd2I?key=vFToHcRzl46s99fckfz_GA" alt=""><figcaption></figcaption></figure>

### Link an existing milestone to a Jira issue

1. Click on the “Link milestone” CTA in the hamburger menu of an existing milestone

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXd7txTcZyf2GY3BfOSf9Dtmjm4w683OwLvv9eupChU4MC-mPhR96Y4FoWIyx4ak1aVHgfHyraC7_Ci1a1EqZ7ulE8OysmgEtwny96xq70YA5enZC7-1EiMA5zPSxsuMsp01YPaMxMs6ttR2wxA9HqVAeb0?key=vFToHcRzl46s99fckfz_GA" alt=""><figcaption></figcaption></figure>

2. 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&#x20;

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                                                                                  |
| <p>Owner</p><p>- If no assignee in Jira, then owner is the person importing the issue</p> | Owner                                                                                    |
| Actual Target date                                                                        | Due Date or Project target date                                                          |
| Actual start date                                                                         | <p>Start date or Project start date<br><br>if not available then Issue creation date</p> |
| 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:

1. Jira configs: define the Jira project and issue type that will be created in Jira
2. Click on the ‘Push to Jira’ at the launch or milestone level

| Push a launch                    | Push a milestone                 |
| -------------------------------- | -------------------------------- |
| ![](/files/RThAKKFurjylG7iBbGsZ) | ![](/files/rS11tpvvKzsYFe038FbK) |

3. 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:

1. Hamburger menu: click on ‘Set workflows’

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXcBBBlNLzgcn8Rsnby5J3FO_OUQu5ibggf7JQPUdJlmcB-y6Esu6wsmPeitwfiYz7Z74IUS44cUhYUV18gBUzkhgOIZqBFJU4c7l4SLk4NrOOsjIxjEvF9ai77L-IDsymALKFG62f9fy4pBeWMRWKwCN3l6?key=vFToHcRzl46s99fckfz_GA" alt=""><figcaption></figcaption></figure>

2. Define the milestone, workflow condition and action&#x20;

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXfk5LMhbPP_FWsDWYngEVzNmVvxsKXWpNARuPcrmmSeXxLfCYgPqpZweALhK3Rv1cE-IMrfYNkWbfmEYI_0L_z1rxgHcwF3jEO4hCriL1DCO5uLT8JRAgS2QeoQ7OmQDflEd0oXuVDX6n07gYUlJS8Dqhoj?key=vFToHcRzl46s99fckfz_GA" alt=""><figcaption></figcaption></figure>

3. 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:&#x20;

* ‘Sync with Jira” enables or disables launch level sync with Jira
* ‘Sync milestones” enables or disables milestones sync with Jira

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXdf18Bhv6cheW68sCzLKcNbey2Ax5SkYinJP0oKnKFjZ6ze1RTxHhf-MzHZPfNv0tycF8qnMOD0qr2Oi55pFGt5VEHZmQxLFa2cnE3Dm9IHATiiLCpHMweKQ8mK-2Mk0dSiPWlHUzZFO3evcnNA3Z5rg8O2?key=vFToHcRzl46s99fckfz_GA" alt=""><figcaption></figcaption></figure>


# Slack

## Overview

Luna's app for Slack lets you create launches or feature requests directly from Slack, set up personal or channel-specific notifications about progress and updates, and sync Slack threads with Luna comments. This integration keeps stakeholders aligned in real-time, enabling them to contribute directly to launches from Slack.

## Getting started&#x20;

### Integration set up

You need to be a Luna admin or maker to connect Luna to Slack. To establish the connection, please follow these steps:&#x20;

1. Go to Settings > Integrations > Slack
2. Click on the “Link” button next to Slack
3. Follow the authentication steps
4. When connected, Luna will display a “Connected” message showing the connection was successful

To disconnect Luna from Slack, in Luna, go to Settings > Integrations > Slack and click on the “Unlink” button next to Slack. Once done, the “Connected” message will go away.

### Notifications set up

You can set up two types of notifications to Slack:&#x20;

#### **Channel-specific notifications**&#x20;

You can connect a launch to a specific channel:&#x20;

1. Go to the launch page and click the bell icon in the top-right corner
2. Select the Slack channel you want to connect to
3. Authenticate and provide consent in Slack
4. Once the channel is connected, Luna will display a "Connected to channelName" message

#### **User-specific notifications**

You can subscribe users to notifications for launch data or specific milestone data:

1. Go to the launch page and click the bell icon in the top-right corner
2. Open the launch or milestone subscription module
3. Add the user's email address to subscribe them to notifications for a launch or a specific milestone

## How Luna works in Slack

Luna's app for Slack covers the following use cases:&#x20;

### Create a new launch&#x20;

The `/create-new-launch` command opens the “New launch” modal. After entering the required information and submitting the form, a new launch will be created in Luna.

This command can also be used by stakeholders to submit feature requests. We recommend creating a template in Luna (e.g., Sales feature requests), which can be selected during the launch creation in Slack.

### Add modules data&#x20;

The `/add-module` command lets users update information linked to various launch modules (e.g., decisions, updates, risks):&#x20;

1. The command prompts users to select the launch and module they want to edit.
2. Based on the selection, a second modal appears, allowing users to update the data for the chosen module.
3. Once submitted, the updated information is synced to Luna.

### View your launches

The `/get-my-launches` command will return the list of upcoming launches where the user is either an owner or a participant. Each launch entry includes:&#x20;

* Key details about the launch for quick access to essential information.
* The option to edit launch data via the “Select an action” dropdown.&#x20;

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXc1IQ9Zyo_VFgPb1F_Byds7RJ44wpVNrle5Jl7YOe3VllFLTeh4rBnR3y0xKTVDWEUSS0jdhhEAUMdoV188WUH8c0FI3N0yVGs87KPkflOHEOG6pU2s3y4Skt3_d9jji7YVeWJVB8QCkB5fB7wNdJx6xiZm?key=RGuoiMlGwcQjfUizflNrGA" alt=""><figcaption></figcaption></figure>

### View modules data

The `/get-launch-module` command allows users to access information related to a specific module:

1. Users will be prompted to select the launch and module they’re interested in.
2. Upon submission, Luna will display the relevant information directly in Slack.

### Weekly launches notifications

Every Monday morning, Luna's app for Slack will send you a summary of the upcoming launches you’re working on, ensuring you stay updated for the week ahead.

You can manage all Slack notifications in Settings > Notifications.

### Sync Slack threads with Luna comments&#x20;

Initiate the Slack thread to Luna comments connection:&#x20;

**Option 1:** copy your launch URL into a Slack channel

* When link unfurls, click on ‘Sync with Luna’s comments’

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXe5rVIZElqwRkI4Y4iHIv5JIzO_xvDikj_ZHBn_wNZFfTsAzLztLiX1PGTgXZ6Voz9yngXTkCGMUxBudDsaDxsF_wEAxkG_C_AIO_zLYgc2hpCi9Ue7ql4_j0S9ayXmJsazq6RgrBSiqBZtdsRB9hzDhN_y?key=RGuoiMlGwcQjfUizflNrGA" alt="" width="563"><figcaption></figcaption></figure>

* Once the connection is established, messages from the Slack thread and comments in the launch's Activity module will sync both ways:

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcwrLgwePPvirwi7n0wtagmaVvCZuhB0HkpUnr6wyfX8JJxdgg8te0K3r4XwfAhpLOY1iVlncIehTeuRUR1RKPubikZUIpubUnss74tgERk0XgrTU1UPvA7cu8bYYb6k569OK1JIrApaJeowylaWBaFr5gi?key=RGuoiMlGwcQjfUizflNrGA" alt=""><figcaption></figcaption></figure>

**Option 2:** from a Slack notification about a key data change:&#x20;

* When link unfurls, click on ‘Sync with Luna’s comments’
* Once the connection is established, messages from the Slack thread and comments in the launch's Activity module will sync both ways:

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfKWVhnVupdp0cTMjdEwgjZbqw12-T06errQDK9UG7o9PWLHHr7RGO8BzGTbscd9sbfyH_1xXveXG10BivEtSG2q3dOh3Z_jUPDfU4Kwxoi78dRBtXH-1gahlJ3gWQ5DJ9ph5yfAxYF2vdn7gwY7fvv2J4?key=RGuoiMlGwcQjfUizflNrGA" alt=""><figcaption></figcaption></figure>

### Notifications in action

#### **Channel-specific notifications**&#x20;

Once a connection is established between a launch and a Slack channel, the channel will receive notifications for the following updates:

* Changes to the launch date, status, or stage
* Additions of new milestones, updates, or decisions

Users can configure these notifications by opting in or out of specific types.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfn8lJxJ8K2OKuRSqGQSxiqFgybEt_YFp44uhkjSC2LnXxMye5yi7d9uLOeNYdE-uOK0fboyQUfBWE9ONJjrlDmT-jlR-nbIIviTErgtzKacVf6A2bMcpsAfJnM6cX7JUx9zbY2?key=RGuoiMlGwcQjfUizflNrGA" alt="" width="563"><figcaption></figcaption></figure>

#### **User-specific notifications**

As a user, you can receive notifications for key events, such as:

* When a launch status changes to "At risk.
* When a milestone is completed

For example, you could subscribe the marketing team to an engineering milestone. Once completed, the marketing team would be notified, prompting them to start their marketing efforts.

You can manage your notifications and opt in or out from the Settings > Notifications page.

## More details

* To learn more about how Luna collects, manages, and stores third-party data, please review our[ Privacy Policy](https://withluna.ai/privacy)
* Luna offers a free trial to help you get started and experience its value firsthand. To explore our paid plans and find the best fit for your team, visit our [pricing page](https://withluna.ai/pricing)


# Asana

## Overview

Integrating Luna with Asana allows you to import your Projects or Tasks and keep them in sync in Luna. Linking your Projects or Tasks to launches in Luna will 1) give visibility to all stakeholders about upcoming launches and 2) allow you to save hours on project management, by keeping Asana and Luna in sync.&#x20;

## How can I connect to Asana

You can connect to Asana on any of the following pages:&#x20;

* Sign up flow
* Create a new launch page
* Settings > Integrations page&#x20;
* Launch page > Milestones > Import from Asana

By clicking on “link” on any of these pages, you will be redirected to the Asana OAuth flow, during which you will consent to the permission scope required by the integration.&#x20;

The connection between Asana and Luna is a workspace to workspace connection. It’s enough for one user (**preferably admin**) to connect to Asana, for all users to be able to leverage the connection in Luna.&#x20;

## How can I import issue(s) as launches in Luna

As a user, you can import any of the following issues: project and task. We recommend you to import issues which need some level of cross-functional and vertical collaboration and visibility:&#x20;

* 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 the All launches page, which will display the issues you have imported&#x20;

## What fields do you import/sync with Asana

The following fields will get imported in Luna and will stay in sync with the launch fields:

| Luna - Launch                                                                                        | Asana - Projects               | Asana - Tasks |
| ---------------------------------------------------------------------------------------------------- | ------------------------------ | ------------- |
| Hamburger menu                                                                                       | Link to project                | Link to task  |
| Title                                                                                                | Name                           | Name          |
| Summary                                                                                              | Project description            | description   |
| <p>Owner</p><p>- If no assignee in Asana, then owner is the person importing the issue</p>           | Project owner in project roles | Assignee      |
| Participants                                                                                         | Project members                | -             |
| <p>Planned launch date</p><p>- If no due date in Asana, then launch date is today’s import date </p> | Due date                       | Due date      |
| Labels                                                                                               | -                              | tags          |
| Luna creation date (log in DB and reflect in timeline)                                               | created\_at                    | created\_at   |

## How can I import issue(s) as milestones in Luna&#x20;

As a user, you can link your Asana issues to new or existing Luna milestones:&#x20;

1. Create new milestones by importing one or more Asana issues into Luna. This is done by clicking on the “Import from Asana” CTA, in the milestones module
2. Link an existing milestone to a Asana issue. This is done by clicking on the “Link milestone” CTA in the hamburger menu of each milestone

Milestones data will remain in sync with any changes made to their linked issue, in Asana.&#x20;

## What milestones fields do you import/sync with Asana?&#x20;

The following fields will get imported in Luna and will stay in sync with the milestones fields:

| Luna - Milestones                                                                          | Asana - Lists | Asana - Tasks |
| ------------------------------------------------------------------------------------------ | ------------- | ------------- |
| Hamburger menu                                                                             | See details   | See details   |
| Name                                                                                       | Name          | Name          |
| <p>Owner</p><p>- If no assignee in Asana, then owner is the person importing the issue</p> | Owner         | Assignee      |
| Target date                                                                                | Due date      | Due date      |
| Child issues                                                                               | List of tasks | N/A           |

## How can I sync a launch with Asana

By default, syncing is enabled. In order to stop syncing your launch and milestones with Asana, you will need to opt out from the syncing option available in the LDP hamburger menu:

<figure><img src="/files/PjdkoVFMrwgaYoouI6gT" alt=""><figcaption></figcaption></figure>

### One sided sync - from Asana to Luna

Luna uses Asana webhooks to keep the data in sync. As a result, a change to an Asana issue field will trigger the corresponding LDP to refresh with the updated Asana issue data. However, changing the data in Luna will not update the issue data in Asana.&#x20;

For example, updating the launch date in Luna, will not update the Asana issue due date. However, updates to the Asana issue due date or any other Asana field (in table above) will be reflected in Luna.&#x20;

## How can I link Asana issues to a Luna template &#x20;

While importing issues from Asana, 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 Asana data complemented with pre-defined modules in the template.&#x20;

When created, launch data will either come from the Asana issue ([data mapping table](#what-fields-do-you-import-sync-with-asana)) or from the template. Some fields clash between the two sources, here’s the import logic:&#x20;

<table><thead><tr><th width="140.1640625">Clashing field</th><th>Rule</th></tr></thead><tbody><tr><td>Summary</td><td><p>The summary section will consist of both the template and the Asana issue summaries. </p><p>After creation, the summary section will remain in sync with the Asana issue description, whenever a change is made. </p></td></tr><tr><td>Labels</td><td><p>Labels will be added from both the Asana tasks and the template. </p><p>After creation, labels coming from Asana will sync as per the above mapping. Labels coming from the template will not be impacted.</p></td></tr></tbody></table>

<br>


# ClickUp

## Overview

Integrating Luna with ClickUp allows you to import your Lists or Tasks and keep them in sync in Luna. Linking your Lists or Tasks to launches in Luna will 1) give visibility to all stakeholders about upcoming launches and milestones details and 2) allow you to save hours on project management, by keeping ClickUp and Luna in sync.&#x20;

## How can I connect to ClickUp

You can connect to ClickUp on any of the following pages:&#x20;

* Sign up flow
* Create a new launch page
* Settings > Integrations page&#x20;
* Launch page > Milestones > Import from ClickUp

By clicking on “link” on any of these pages, you will be redirected to the ClickUp OAuth flow, during which you will consent to the permission scope required by the integration.&#x20;

The connection between ClickUp and Luna is a workspace to workspace connection. It’s enough for one user (preferably admin) to connect to ClickUp, for all users to be able to leverage the connection in Luna.&#x20;

## How can I import issue(s) as launches in Luna

As a user, you can import any of the following issues: list and task. We recommend you to import issues which need some level of cross-functional and vertical collaboration and visibility:&#x20;

* 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 the All launches page, which will display the issues you have imported&#x20;

## What launch fields do you import/sync with ClickUp

The following fields will get imported in Luna and will stay in sync with the launch fields:

| Luna - Launch                                                                                          | ClickUp - Lists                                         | ClickUp - Tasks                                         |
| ------------------------------------------------------------------------------------------------------ | ------------------------------------------------------- | ------------------------------------------------------- |
| Hamburger menu                                                                                         | Link to list                                            | Link to task                                            |
| Title                                                                                                  | Name                                                    | Name                                                    |
| Summary                                                                                                | <p>Description</p><p>\[Next] Fix formatting</p>         | <p>Description</p><p>\[Next] Fix formatting</p>         |
| <p>Owner</p><p>- If no assignee in ClickUp, then owner is the person importing the issue</p>           | Owner                                                   | -                                                       |
| <p>Planned launch date</p><p>- If no due date in ClickUp, then launch date is today’s import date </p> | Due date                                                | Due date                                                |
| Stage                                                                                                  | -                                                       | Status                                                  |
| <p>Priority</p><ul><li>Low = Low</li><li>Medium = Normal</li><li>High = High, Urgent</li></ul>         | Priority                                                | Priority                                                |
| Labels                                                                                                 | -                                                       | Tags                                                    |
| Luna creation date (log in DB and reflect in timeline)                                                 | <p>Start date, if available</p><p>Else, created\_at</p> | <p>Start date, if available</p><p>Else, created\_at</p> |

## How can I import issue(s) as milestones in Luna

As a user, you can link your ClickUp issues to new or existing Luna milestones:&#x20;

1. Create new milestones by importing one or more ClickUp issues into Luna. This is done by clicking on the “Import from ClickUp” CTA, in the milestones module&#x20;
2. Link an existing milestone to a ClickUp issue. This is done by clicking on the “Link milestone” CTA in the hamburger menu of each milestone

Milestones data will remain in sync with any changes made to their linked issue, in ClickUp.&#x20;

## What milestones fields do you import/sync with ClickUp

The following fields will get imported in Luna and will stay in sync with the milestones fields:

| Luna  - Milestones                                                                           | ClickUp - Lists | ClickUp - Tasks |
| -------------------------------------------------------------------------------------------- | --------------- | --------------- |
| Hamburger menu                                                                               | See details     | See details     |
| Name                                                                                         | Name            | Name            |
| <p>Owner</p><p>- If no assignee in ClickUp, then owner is the person importing the issue</p> | Owner           | -               |
| Target date                                                                                  | Due date        | Due date        |
| Stage                                                                                        | -               | Status          |
| \[Next] Child issues                                                                         | List of tasks   | -               |

## How can I sync a launch with ClickUp

By default, syncing is enabled. In order to stop syncing your launch and milestones with ClickUp, you will need to opt out from the syncing option available in the LDP hamburger menu:

<figure><img src="/files/n2Jz7znXJx7EglJ47ETw" alt=""><figcaption></figcaption></figure>

### One sided sync - from ClickUp to Luna

Luna uses ClickUp webhooks to keep the data in sync. As a result, a change to a ClickUp issue field will trigger the corresponding LDP to refresh with the updated ClickUp issue data. However, changing the data in Luna will not update the issue data in ClickUp.&#x20;

For example, updating the launch date in Luna, will not update the ClickUp issue due date. However, updates to the ClickUp issue due date or any other ClickUp field (in table above) will be reflected in Luna.&#x20;

\[Backlog] We’re exploring launching a 2-way sync and more controls on data mapping and syncing

## How can I link ClickUp issues to a Luna template &#x20;

While importing issues from ClickUp, 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 ClickUp data complemented with predefined modules in the template.&#x20;

When created, launch data will either come from the ClickUp issue ([data mapping table](#what-milestones-fields-do-you-import-sync-with-clickup)) or from the template. Some fields clash between the two sources, here’s the import logic:&#x20;

<table><thead><tr><th width="139.9296875">Clashing field</th><th>Rule</th></tr></thead><tbody><tr><td>Summary</td><td><p>The summary section will consist of both the template and the ClickUp issue summaries. </p><p>After creation, the summary section will remain in sync with the ClickUp issue description, whenever a change is made. </p></td></tr><tr><td>Labels</td><td><p>Labels will be added from both the ClickUp tasks and the template. </p><p>After creation, labels coming from ClickUp will sync as per the above mapping. Labels coming from the template will not be impacted.</p></td></tr></tbody></table>

\ <br>


# Google Docs

## Overview

Our goal is to have you spend less time per week on reporting. Luna uses Google Docs to create different kinds of reports (e.g., weekly launch summary), which you can quickly edit and share with the relevant stakeholders.&#x20;

## How can I connect to Google Docs

You can connect to Google Docs on any of the following pages:&#x20;

* Sign up flow
* Any **launch page > Hamburger menu > Summary**
* **Settings > Integrations** page&#x20;

Any of the three options above will redirect you to the Google Docs oAuth flow, during which you will consent to the permission scope required by the integration.&#x20;

The connection between Google Docs and Luna is a user to user connection. Each Luna user will have to independently connect their Luna workspace to their Google Docs. &#x20;

## How can I create a launch weekly summary in Google Docs &#x20;

Any “admin” or “maker” being an owner or participant of a launch, can trigger the weekly summary in two ways:&#x20;

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcA2kARgXQI9dP21MUfo4NDVDNEvz2e_2HsYixFc-A-54zru6P_-muS4wMm-KwpR__r-Aet-Wd27t8mwI9S7KFVJNRC8pPag9xr6MxlatTBOxupQCTg1aYxYR2WDo_UfMUa-f6UJwBxzKpfRLgZcQSK8bI0?key=fzGmYXb4rKEal_h2iFz1uw" alt="" width="563"><figcaption></figcaption></figure>

### 1- Manual trigger&#x20;

The weekly summary can be triggered manually at any point in time. In a launch page:&#x20;

* Click on **hamburger menu > Summary**
* If not connected to Google Docs, you will be taken through the oAuth flow
* A Google Docs will open, filled out with a summary of the launch. Data reflects this week’s progress.
* You are the owner of that Google Docs. Anyone in your organization will have comment rights, as long as they can access the link.&#x20;
* Each launch weekly summary will be created in a Google Drive folder called “Launch weekly summary - Luna”

### 2- Automated trigger &#x20;

The weekly summary can be triggered automatically, each end of week, by Luna. In a launch page:&#x20;

* Click on **hamburger menu > Weekly summary**
* If not connected to Google Docs, you will be taken through the oAuth flow
* At the end of each week, Luna will create a launch weekly summary Google Doc that will be stored in your drive.&#x20;
* Luna will also add a link to that Google Doc in your “resources” tab

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfCUno5Ia_qRiv2TfGWwk7yiC5P55m9CxeWosEEdu0VUVtadbycP5olUE9_L1huffY30OOjOevkzoKznpkpDCArCwYwu7Xu8jHgt-1YiJhHcTFtePAVMCIRbnm5bTUmGfr5dM5ck1RdQaCENQE3beCOWjTb?key=fzGmYXb4rKEal_h2iFz1uw" alt="" width="563"><figcaption></figcaption></figure>

## Example - launch weekly summary  &#x20;

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfzlpuMb2bbX4E2MCps69CiqOPEcOEcDumwwCIoBpfN7v1PbkZKVeapYgp4RwMFhZeOYiTN7LbgDwvTRGb65iVrATBCZ63S3QGxLThhsE1d6LUXOzc7vdCqCJu0lo9mPST0tX4jGr-iz2059IPC1m6xKFvA?key=fzGmYXb4rKEal_h2iFz1uw" alt="" width="563"><figcaption></figcaption></figure>

<br>


# Contact us

For any questions or enquiries, please contact <support@withluna.ai>