Looking for documentation for moving from jira issues to next gen jira issues in a jira salesforce i

[JoAnn Bartlett]

Do you have any documentation on migrating from the jira issues component to the next gen jira issues component in Salesforce for the Jira/Salesforce integration?

[OpsHub - Enterprise class Integration and Migration Solutions for Jira]

Hi John. 

There isn’t official Atlassian documentation specifically for Salesforce–Jira integrations during next-gen migration, but here’s what to keep in mind.

When moving from classic to next-gen Jira projects:

• Issue types, custom fields, and workflows may not carry over automatically
• Next-gen projects use team-managed configurations, which may break existing Salesforce field mappings
• Integrations often need to be reconfigured to match the new schema and issue structure

OpsHub Integration Manager. (Community (free edition) an Atlassian Solutions Partner supports this kind of transition by:

• Allowing re-mapping of issue types and fields between Salesforce and the new Jira project
• Preserving traceability and sync logic during the switch
• Ensuring that updates from Salesforce still flow to the correct Jira items—without data loss or duplication

Hope this helps!

[Brant Schroeder]

@JoAnn Bartlett welcome to the Atlassian community

Depending on the app you are using to integrate this has more to do with the project type you are connecting Salesforce to.  A next gen issue is found in a team managed project and a company managed project uses standard Jira issues.  I would suggest checking the applications documentation to better understand how it interacts with Jira.