Appfire Documentation Home
Spaces
Apps
Templates
Create
Classic Connector for Salesforce & Jira
All content
Blogs
Calendars
Space settings
Content
Results will update as you type.
•
Classic Connector for Salesforce & Jira sunset
•
Classic Connector and NextGen Connector for Salesforce & Jira comparison
•
Classic Connector for Salesforce and Jira sunset FAQ
Administrator guide
User guide
Quick start guide
Migrating from Classic Connector for Salesforce & Jira server to cloud
Getting help
Knowledge Base
Errors and Error Messages
Compatibility/Features
•
Can I Move Existing Linked or Associated JIRA Issues to Other Projects?
•
What limitations are there?
•
Do You Support Objects Other Than Cases?
•
I Am Unable to See VisualForce (Fetch Endpoint) Using Chrome/Firefox/IE
•
What's New in Version 5?
•
What Versions of Salesforce are Compatible with the Connector?
•
Is version 5.4 of the Connector backwards compatible with 5.3?
•
Salesforce and JIRA Server Connector Versus Cloud Connector Comparison
•
Is Classic Connector for Salesforce & Jira impacted by Multi-Factor Authentication enforcement by Salesforce ?
•
Installing the Connector on JIRA 4.3 to JIRA 4.4.5
Linking
Configuration
Security
Mapping
Synchronization
Connection
General
Migration
•
Contact Us
•
Using the Diagnostic Tool
Migrating Connector for Salesforce & Jira from Classic to NextGen
Apps
Comala Publishing
Comala Document Management
Classic Connector for Salesforce & Jira
/
/
Compatibility/Features
/
Can I Move Existing Linked or Associated JIRA Issues to Other Projects?
Can I Move Existing Linked or Associated JIRA Issues to Other Projects?
Jeff Gleeson
Ted Mahsun (Deactivated)
Li Xuan Liew (Deactivated)
Owned by
Jeff Gleeson
Last updated:
Sept 20, 2023
by
Jeff Gleeson
1 min read
Loading data...
{"serverDuration": 23, "requestCorrelationId": "acbc76bb04bc4261b4aea08c003bf101"}