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

JIRA Portfolio: why stories aren't moved from sprint to sprint after one is finished

Hi!

We created custom sprints for a team. Portfolio automatically assigned stories to sprints. But when the first sprint time was over, Portfolio didn't move stories to the next sprint and didn't signalized that we failed.

Could anybody explain why, please? What is the reason of using Portfolio if it doesn't signalize about such failure and doesn't move stories on and on.

http://prntscr.com/868iaj - printscreen

The same situation is with automatic sprints (sprint1 ... sprintN) http://prntscr.com/868mak

 

2 answers

1 accepted

2 votes
Answer accepted
Martin Suntinger
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 18, 2015

Hi Vladimir, thanks for raising this question - the way it is designed right now is that stories move on only as part of explicit plan updates (Plan > Update from date) - this sets a new start date from when to schedule, and stories will be scheduled only from that date forward. Currently the start date of your plan is Aug 10, so work will be scheduled starting from there. If you run a plan udpate and set the new start date of the plan to let's say Aug 20, sprints before Aug 20 will be ignored and items scheduled into sprints after that. 

However, all that said we're working on a tighter integration with JIRA / JIRA Agile as part of addressing our top-voted issues over the coming months (https://jira.atlassian.com/browse/JPO-10https://jira.atlassian.com/browse/JPO-42https://jira.atlassian.com/browse/JPO-13)  which will significantly simplify and automate this update process. Best, Martin (Product Manager for JIRA Portfolio) 

@Martin Suntinger thanks a lot. Really quick and helpful answer. You do a great job with Portfolio! Thanks once again and have a good day!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events