Jira Status Mapping

How to get there: Go to Settings in the sidebar → Integrations tab (under Other) → Jira section → Status Mapping settings.

Learn how to map ProductLift statuses to Jira statuses for bi-directional synchronization, ensuring feedback and development tracking stay aligned across both platforms.

What is Jira Status Mapping?

Jira Status Mapping allows you to connect ProductLift post statuses with Jira issue statuses, enabling automatic synchronization when statuses change in either system. When a ProductLift post moves to "Planned," the linked Jira issue can automatically move to "In Progress," and vice versa.

Benefits:

• Automatic Sync: Status changes propagate between systems
• Single Source of Truth: No manual status updates needed
• Team Alignment: Product and engineering stay synchronized
• Reduced Admin: Less manual tracking and updates

[Screenshot: Status mapping interface showing ProductLift statuses on left mapped to Jira statuses on right with connecting arrows]

Prerequisites

Requirements:

1. Jira Integration Active:

   • ProductLift connected to Jira instance
   • API credentials configured
   • Jira project selected

2. Jira Permissions:

   • Edit issues permission
   • Transition issues permission

3. ProductLift Plan:

   • Pro or Enterprise (Jira integration feature)

See Integrate with Jira for initial Jira setup.

Understanding Status Mapping

ProductLift Statuses

Your Feedback Workflow:

ProductLift statuses represent stages in your feedback lifecycle:

Example Statuses:

• New
• Under Review
• Planned
• In Progress
• Testing
• Released
• Won't Build

Your portal may have different status names (customizable).

[Screenshot: ProductLift status list showing custom statuses with icons and colors]

Jira Statuses

Your Development Workflow:

Jira statuses represent stages in your development process:

Common Jira Statuses:

• To Do
• In Progress
• Code Review
• Testing
• Done
• Won't Do

Note: Jira workflows vary by project and configuration.

[Screenshot: Jira workflow diagram showing status transitions with arrows]

Status Mapping Concept

Mapping = Relationship:

A status mapping creates a relationship between ProductLift and Jira statuses:

ProductLift "Planned"  ←→  Jira "To Do"
ProductLift "In Progress"  ←→  Jira "In Progress"
ProductLift "Released"  ←→  Jira "Done"

When Mapped:

• ProductLift post moves to "Planned" → Jira issue moves to "To Do"
• Jira issue moves to "In Progress" → ProductLift post moves to "In Progress"

Bi-directional synchronization keeps both systems aligned.

[Screenshot: Diagram showing bi-directional arrows between ProductLift and Jira with example status transitions]

Setting Up Status Mapping

Step 1: Access Jira Settings

Navigate to Jira Integration:

Settings → Integrations → Jira → Status Mapping

Or: Settings → Jira → Configure Status Mapping

[Screenshot: Settings sidebar with Jira integration highlighted, showing Status Mapping option]

Step 2: View Existing Statuses

Status Lists Displayed:

Left Column: ProductLift Statuses

• All statuses configured in your portal
• Sorted by workflow order

Right Column: Jira Statuses

• All statuses from connected Jira project
• Fetched from Jira API automatically

[Screenshot: Two-column interface showing ProductLift statuses list on left, Jira statuses list on right]

Step 3: Create Mappings

Map Each Corresponding Status:

Click "Add Mapping"

Select ProductLift Status:

• Dropdown showing all ProductLift statuses
• Example: "Planned"

Select Jira Status:

• Dropdown showing all Jira statuses
• Example: "To Do"

Set Sync Direction:

• Both Ways (Recommended): Changes sync in both directions
• ProductLift → Jira Only: ProductLift drives Jira
• Jira → ProductLift Only: Jira drives ProductLift

Save Mapping

[Screenshot: Add mapping dialog showing ProductLift status dropdown, Jira status dropdown, sync direction radio buttons, and Save button]

Step 4: Configure All Mappings

Recommended Mappings:

Not All Statuses Need Mapping:

• "New" posts may not have Jira issues yet
• Some ProductLift statuses are internal only
• Map only relevant workflow stages

[Screenshot: Status mapping table showing completed mappings with edit/delete actions]

Step 5: Test Mapping

Verify Synchronization:

1. Find ProductLift post linked to Jira issue
2. Change ProductLift post status to mapped status
3. Wait 5-10 seconds (webhook processing)
4. Check Jira issue status updated
5. Try reverse: Change Jira status, verify ProductLift updates

Troubleshooting:

If status doesn't sync:

• Check mapping configured for that status
• Verify Jira connection active
• Review sync logs (Settings → Jira → Logs)
• Confirm Jira user has permission to transition issues

Status Mapping Examples

Example 1: Standard Workflow

Scenario: Agile development team with standard Jira workflow.

Mappings:

ProductLift            Jira               Direction
-----------            ----               ---------
Under Review     →     Backlog            Both Ways
Planned          →     Selected           Both Ways
In Progress      →     In Progress        Both Ways
Testing          →     In QA              Both Ways
Released         →     Done               Both Ways
Won't Build      →     Closed             ProductLift → Jira Only

Workflow:

1. Customer submits feedback → "New" in ProductLift (no Jira issue)
2. Admin reviews, creates Jira issue → "Under Review" / "Backlog"
3. Prioritized for sprint → "Planned" / "Selected"
4. Development starts → "In Progress" / "In Progress"
5. Testing begins → "Testing" / "In QA"
6. Ships to production → "Released" / "Done"

[Screenshot: Workflow diagram showing post journey through ProductLift and Jira statuses side-by-side]

Example 2: Simplified Workflow

Scenario: Small team, simple workflow, fewer statuses.

Mappings:

ProductLift            Jira               Direction
-----------            ----               ---------
Planned          →     To Do              Both Ways
In Progress      →     In Progress        Both Ways
Released         →     Done               Both Ways

Benefits:

• Fewer mappings to maintain
• Clearer workflow
• Works for smaller teams

Example 3: Engineering-Driven

Scenario: Engineering team updates Jira, ProductLift follows.

Mappings:

ProductLift            Jira               Direction
-----------            ----               ---------
Planned          →     To Do              Jira → ProductLift
In Progress      →     In Progress        Jira → ProductLift
Released         →     Done               Jira → ProductLift

Use Case:

• Engineers manage workflow in Jira
• Customers see status updates in ProductLift automatically
• Product managers don't need to manually update ProductLift

Example 4: Customer-Facing Only

Scenario: Hide internal development stages from customers.

Mappings:

ProductLift            Jira               Direction
-----------            ----               ---------
Planned          →     (any)              ProductLift → Jira
Released         →     Done               Both Ways

Internal Jira Statuses Not Mapped:

• Code Review
• Testing
• Deployment

Customer View in ProductLift:

• Sees "Planned" (we're building it)
• Sees "Released" (it's done)
• Internal complexity hidden

Synchronization Behavior

When Sync Occurs

ProductLift → Jira:

When admin changes ProductLift post status:

• Webhook sent to Jira API
• Jira issue transitioned to mapped status
• Transition happens within 5-10 seconds

Jira → ProductLift:

When Jira issue status changes:

• Jira webhook notifies ProductLift
• ProductLift post status updated to mapped status
• Update happens within 5-10 seconds

[Screenshot: Sync timeline showing status change → webhook → API call → status update with timestamps]

Status Transition Validation

Jira Workflow Constraints:

Jira workflows may have restrictions:

• Can't transition directly from "To Do" to "Done"
• Must go through intermediate statuses

What Happens:

• ProductLift attempts to transition Jira issue
• If invalid transition, error logged
• ProductLift status still changes (one-way)
• Admin notified of sync failure

Solution:

• Map only valid Jira transitions
• Or use intermediate status mappings
• Or adjust Jira workflow to allow transitions

Conflict Resolution

If Status Changes in Both Systems:

Rare but possible (simultaneous changes):

Conflict Resolution:

• Last change wins (timestamp-based)
• Most recent status update applies to both systems
• Conflict logged for review

Best Practice:

• Choose primary system for status changes
• Use one-way sync if conflict-prone
• Review conflict logs periodically

Advanced Mapping Features

Conditional Mapping

Map Based on Conditions:

Settings → Jira → Advanced Status Mapping

Condition Examples:

By Category:

IF ProductLift Category = "Mobile App"
   AND Status = "In Progress"
THEN Jira Status = "Mobile Development"

By Priority:

IF ProductLift Post has Tag "urgent"
   AND Status = "Planned"
THEN Jira Status = "Sprint Backlog"
ELSE Jira Status = "Product Backlog"

[Screenshot: Conditional mapping interface showing IF-THEN rule builder with condition fields and action selectors]

Multi-Project Mapping

Different Mappings per Jira Project:

If you sync posts to multiple Jira projects:

Setup:

1. Configure mapping for each Jira project separately
2. Specify project in mapping rule
3. Posts route to correct project with correct status mapping

Example:

ProductLift Category = "Mobile App"
  → Jira Project: MOB (Mobile Project)
  → Status Mapping: Planned → MOB:Backlog

ProductLift Category = "API"
  → Jira Project: API (API Project)
  → Status Mapping: Planned → API:To Do

Custom Field Sync

Beyond Status:

Sync more than just statuses:

Additional Sync Options:

• Priority: ProductLift → Jira priority field
• Assignee: Jira assignee → ProductLift assigned user
• Labels: ProductLift tags → Jira labels
• Due Date: Jira due date → ProductLift custom field

Configure: Settings → Jira → Field Mapping

[Screenshot: Field mapping interface showing ProductLift fields mapped to Jira fields]

Monitoring and Troubleshooting

Sync Logs

View Sync Activity:

Settings → Jira → Sync Logs

Log Information:

• Timestamp
• ProductLift post ID and title
• Jira issue key
• Status change (from → to)
• Sync direction
• Success/failure
• Error message (if failed)

[Screenshot: Sync logs table showing recent sync events with status icons and error details]

Common Sync Issues

Issue: Status Not Syncing

Causes:

• Mapping not configured for that status
• Jira connection inactive
• Invalid status transition in Jira workflow
• Insufficient Jira permissions

Solution:

1. Verify mapping exists (Settings → Jira → Status Mapping)
2. Check Jira connection (Settings → Jira → Connection Status)
3. Review Jira workflow (can status A transition to status B?)
4. Verify Jira user permissions (can edit and transition issues)
5. Check sync logs for specific error

Issue: Sync Delay

Causes:

• Webhook processing queue
• Network latency
• Jira API rate limiting

Solution:

• Normal: 5-10 seconds is expected
• If > 1 minute: Check Jira API status
• If persistent: Contact ProductLift support

Issue: Wrong Status After Sync

Causes:

• Incorrect mapping configured
• Multiple mappings conflict
• Jira workflow forced different transition

Solution:

• Review status mapping configuration
• Check for duplicate or conflicting mappings
• Verify Jira workflow allows intended transition
• Update mapping to correct status

Sync Health Dashboard

Monitor Integration Health:

Settings → Jira → Dashboard

Health Metrics:

• Sync success rate (last 30 days)
• Average sync time
• Failed syncs count
• Last successful sync timestamp
• Jira API connection status

Alert Thresholds:

• 🟢 Green: >95% success rate
• 🟡 Yellow: 85-95% success rate
• 🔴 Red: <85% success rate

[Screenshot: Sync health dashboard showing success rate gauge, sync time chart, and alert indicators]

Best Practices

Map Essential Statuses Only

Don't Over-Map:

• Map 3-5 key statuses (not all 10+)
• Focus on customer-visible states
• Skip internal development stages

Essential Mappings:

• "Planned" → Jira "To Do" (committed to build)
• "In Progress" → Jira "In Progress" (being built)
• "Released" → Jira "Done" (shipped)

Use Bidirectional Sync Carefully

When to Use Both Ways:

• Small team, single source of truth unclear
• Engineers and PMs both manage statuses
• Full transparency needed

When to Use One-Way:

• Clear ownership (PMs manage ProductLift, engineers manage Jira)
• Avoid conflicts
• Simpler to reason about

Recommendation: Start one-way, add bidirectional if needed.

Document Your Mapping

Create Internal Guide:

Document for your team:

Status Mapping Guide

ProductLift "Under Review" ↔ Jira "Backlog"
  - Both ways sync
  - Happens when: Admin reviews and prioritizes

ProductLift "Planned" ↔ Jira "Selected for Development"
  - Both ways sync
  - Happens when: Added to sprint or roadmap

ProductLift "In Progress" ↔ Jira "In Progress"
  - Both ways sync
  - Happens when: Engineer starts work

ProductLift "Released" ↔ Jira "Done"
  - Both ways sync
  - Happens when: Deployed to production

Share with team so everyone understands the workflow.

Regular Mapping Audits

Monthly Review:

1. Check sync logs for failures
2. Review mapping configuration still accurate
3. Update mappings if workflow changed
4. Test sync with sample post
5. Update documentation if needed

Handle Jira Workflow Changes

When Jira Workflow Changes:

If Jira statuses renamed or workflow restructured:

1. Update status mappings in ProductLift
2. Test sync with each mapping
3. Notify team of changes
4. Update internal documentation

Avoid Mapping to Deleted Statuses:

• Sync will fail if Jira status no longer exists
• Remove obsolete mappings

Azure DevOps Alternative

Azure Boards Integration:

ProductLift also supports Azure DevOps Boards (similar to Jira).

Status Mapping:

Same concept, different platform:

• ProductLift statuses → Azure Boards states
• Bidirectional sync available
• Configuration: Settings → Integrations → Azure DevOps

See Azure DevOps documentation for Azure-specific details.

[Screenshot: Azure DevOps status mapping interface showing similar layout to Jira mapping]

Related Articles

Jira Integration:

• Integrate with Jira - Initial Jira setup and connection
• Webhooks - Webhook configuration details
• ProductLift API - API-based integration

Workflow:

• Feature Launch Workflow - Using Jira sync in feature lifecycle
• Kanban Board Management - Status visualization
• Understanding Boards and Workflow - ProductLift status configuration