Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
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

Join now to unlock these features and more

Stop Jira Portfolio from creating sprints

Kimball Johnson
Kimball Johnson Jun 11, 2018

I need to turn off Portfolio's automatic sprint generation until I can find sufficient documentation to be able to control it.

I'm getting projects and teams that show between 20 and 50 sprints  and then having to deal with sprint conflicts. All of this is stuff i do not want to deal with.

There must be a way to turn it off and on... yes?

Thanks,

Kimball

Answer
Watch
Like Be the first to like this
449 views

1 answer

0 votes
Jovanna Pugh
Jovanna Pugh Feb 27, 2019 • edited

I am having problems with this as well.  In the screenshot I attached, Sprint 69 is the last actual sprint that exists in Jira.  Portfolio has auto-generated Sprint 8 and beyond.  In addition, they're all empty.  How can I stop Portfolio from automatically creating these empty sprints??

 

image.png

View More Comments
Jovanna Pugh
Jovanna Pugh Feb 27, 2019

I figured this out!  We were incorrectly including a release from another project that has a release date of December 2019.  The project this plan is related to doesn't have cards planned out that far.  I assume that Portfolio looks the release dates for all included versions and creates sprints in the future to match.  As soon as I removed the release that didn't belong, the empty sprints went away.  

Like
Reply

Suggest an answer

Log in or Sign up to answer
Portfolio for Jira
Advanced planning
TAGS
AUG Leaders

Atlassian Community Events

See all events