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

JIRA portfolio - stories are taken in concurrent

Edited
Mohamed Ali
Mohamed Ali Apr 25, 2018

After creating the plan, different stories and epics taken concurrently. I want that to be changed in a way once story A is complete Story b can be taken.

Example: 

Story A (100 story points) and Story B (100 story points)

Team velocity: 100

portfolio schedule showed like : Sprint 1 - Story A and B (each 50 points burned)

Sprint 2: both stories are done.

 

Expected: Sprint 1: Story A complete and Sprint 2: Story B complete

 

Can you please help on how to change the settings to incorporate this?

Answer
Watch
Like Be the first to like this
365 views

1 answer

0 votes
Earl McCutcheon
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 08, 2018

Hello Mohamed,

It sounds like Story B has been manually added to the same sprint that Story A is part of.  And when Manual association is in place this overrides the calculation performed by portfolio.

Check out the Scheduling Behavior Documentation for more details on this.

-Earl

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