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?
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events