In a case where an issue is carried over to multiple sprints, I've found that the connector will only pull the latest sprint over on the Issue. So if Issue A was not completed on Sprint 1 or Sprint 2, but was completed on Sprint 3, Issue A in the Smartsheet is only associated with Sprint 3.
As a workaround, I'm recommending our team stops carrying issues to multiple sprints. Jira addresses this by advising users clone a story if no work was completed and they want to add it to the next sprint, or split it if some work was completed.
The problem comes in when a story is cloned. Orig story moves to the backlog and clone story moves to the next sprint. Orig story is not ever going to be worked on and we really don't want it in the backlog, we just want it reflected as Not Completed at the end of that Sprint. Any recommendations?
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Become an effective Jira admin
Manage global settings and shared configurations called schemes to achieve goals more quickly.
Streamline Jira administration with effective governance
Improve how you administer and maintain Jira and minimize clutter for users and administrators.
Learning Path
Become an effective Jira software project admin
Set up software projects and configure tools and agile boards to meet your team's needs.