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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Ignore old sprint dates on my future plans?

Occasionally, we have a task fall out of a current sprint and into the backlog. We choose not to close it because it may have some value in the future should we decide to prioritize it again. 

These tasks are then flagged with warnings on our Roadmap, because they inherit the end date from that closed sprint which falls into the past. 

I find myself spending time putting arbitrary future end dates on these, like Dec 31 2021. While it's annoying to do this, it's less annoying than explaining a "false positive" warning on the roadmap to a stakeholder. 

Wondering if Roadmaps can/should be updated to ignore past sprint start and end dates on open issues? 

1 comment

Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 04, 2021

Hi @Stephen Sayler ,

I think this is the same question that came up here:

Rather than repeating myself, it might be worth having a read of that thread and letting me know if that answers your question?



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events