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,462,950
Community Members
 
Community Events
176
Community Groups

When an issue spans multiple sprints, how can reflect the issue as Not Completed in Older Sprints?

Example: Story A is in Sprint 1 but not completed, so they roll it over to Sprint 2.  Story A also isn't completed in Sprint 2, so they roll it over to Sprint 3 where it is completed. 

Jira's Sprint Reports for Sprint 1 and 2 show Story A in the 'Issues Not Completed' section.  The Sprint Report for Sprint 3 shows Story A in the 'Completed' section.  I've set up the Connector workflow to pull all Issues Grouped by Sprint.  Problem is Story A is only reflected as 'Closed' in Sprint 3, it's not pulled into the Sprint 1 or 2 Groups so I'm not able to reflect that it was attempted, but not Completed.  Any thoughts?  Thanks so much!

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events