Integrated Data
Jira Cloud
What this page covers: A complete reference mapping every Jira Cloud field to its Mosaic equivalent. Use this guide when configuring your integration, verifying synced data, or troubleshooting discrepancies.
| Integration type | Cloud (Jira REST API v3) |
| Setup complexity | Low |
| Prerequisite | Jira Cloud Integration Setup |
How Data Flows
Jira Cloud (REST API v3) → Mosaic Sync Engine (field mapping) → Mosaic (7 synced data types)
Mosaic pulls data from Jira Cloud using the Jira REST API v3. Projects, issue types, and users are mapped into Mosaic's project hierarchy. Jira's issue type hierarchy determines how items map to Mosaic:
Jira Issue Hierarchy
Typical Jira Issue Hierarchy:
- Initiative (currently not supported in Mosaic)
- Epic
- Story, Task, Bug
- Subtask
As a parent issue, an epic can have stories, tasks, and bugs as child issues. A task can have subtasks as child issues. A subtask cannot have any child issues.
Integrated Data Types
The integration syncs 7 data categories from Jira Cloud into Mosaic:
| # | Data Type | Description |
|---|---|---|
| 1 | Employees | Jira users mapped to Mosaic team members |
| 2 | Portfolios | Jira project categories or groupings |
| 3 | Clients | Client records derived from Jira project metadata |
| 4 | Projects | Jira projects (with optional Epic-as-Project mapping) |
| 5 | Phases | Epics (default) or Stories mapped as project phases |
| 6 | Scopes | Stories (default) or Epics mapped as project scopes |
| 7 | Tasks | Other issue types (Story, Task, Bug — excludes Subtasks) |
This list may expand as new features are added. If new features require additional permissions, your Customer Success Manager will reach out to your team.
Reading the Field Mapping Tables
Symbol legend for technical tables
The Technical Reference tabs below use a shorthand notation for API sources. Read this legend before reviewing the mappings.
| Symbol | Meaning | Example |
|---|---|---|
. | API object field reference | Issue.fields.summary = the summary field from the Issue object |
OR | Configurable — an integration setting selects which | Epic OR Story = your configuration chooses one |
Detailed Field Mappings
Jump to a section: Employees | Portfolios | Clients | Projects | Phases | Scopes | Tasks
Employees
| What Syncs to Mosaic | Where It Comes From in Jira |
|---|---|
| Employee Name | The user's display name |
| Employee Email | The user's email address |
Portfolios
| What Syncs to Mosaic | Where It Comes From in Jira |
|---|---|
| Portfolio | Jira project categories or groupings used to organize projects |
Clients
| What Syncs to Mosaic | Where It Comes From in Jira |
|---|---|
| Client | Client records derived from Jira project metadata |
Projects
| What Syncs to Mosaic | Where It Comes From in Jira |
|---|---|
| Project Title | The Jira project name |
| Project Number | The Jira project key |
| Project Description | The Jira project description |
| Start Date | The project start date |
| End Date | The project end date |
Epic-as-Project mapping: When configured, Jira Epics can also be mapped as Projects. In this case, Epic summary, key, description, start/end dates, and status are used.
Phases
Phases are mapped from Epics by default, but can be configured to use Stories instead.
| What Syncs to Mosaic | Where It Comes From in Jira |
|---|---|
| Phase Title | The Epic summary (or Story summary if configured) |
| Phase Number | The Epic key (or Story key if configured) |
| Phase Description | The Epic description |
| Start Date | The Epic start date |
| End Date | The Epic due date |
| Status | The Epic status (mapped — see status mapping below) |
| Estimated Hours | The Story estimated hours (when Stories are used as Phases) |
Scopes
Scopes are mapped from Stories by default, but can be configured to use Epics instead.
| What Syncs to Mosaic | Where It Comes From in Jira |
|---|---|
| Scope Title | The Story summary (or Epic summary if configured) |
| Scope Number | The Story key (or Epic key if configured) |
| Scope Description | The Story description |
| Start Date | The Story start date |
| End Date | The Story due date |
| Status | The Story status (mapped — see status mapping below) |
| Hours | The Story estimated hours |
Tasks
Tasks are mapped from other issue types (Story, Task, Bug) — excludes Subtasks.
| What Syncs to Mosaic | Where It Comes From in Jira |
|---|---|
| Task Title | The issue summary |
| Task Number | The issue key |
| Task Description | The issue description |
| Start Date | The issue start date |
| End Date | The issue due date |
| Status | The issue status (mapped — see status mapping below) |
| Assignee | The issue assignee |
| Assigner | The issue reporter (Jira Reporter field) |
| Hours | The estimated hours on the issue |
Status Mapping
Mosaic maps Jira statuses for Projects, Epics, and Issues as follows:
| Jira Status (Category) | Mosaic Status |
|---|---|
| To Do | Not Started |
| In Progress | Active |
| Done | Complete |
Custom statuses: For custom statuses in Jira (e.g.,
Selected For Development), Mosaic maps them based on their corresponding Status Category ("To Do", "In Progress", "Done") in Jira. This ensures an effective and clear understanding of your project's progress across both platforms.
Jira Documentation Links
A consolidated reference of all Jira documentation referenced in this guide:
| Topic | Link |
|---|---|
| REST API v3 Overview | Jira Cloud REST API |
| Users | Users API |
| Projects | Projects API |
| Project Categories | Project Categories API |
| Issues | Issues API |
| Issue Search | Issue Search API |
| Issue Types | Issue Types |
Related Documentation
Updated 8 minutes ago