Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,076
Community Members
 
Community Events
176
Community Groups

Jira to Smartsheet Connector-How to handle 1:1 relationship of Sprint to Issue?

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?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events