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

What drives the scheduling for Portfolio for Jira?

I am trying to put together a road map of work for Q4 2019 and Q1 2020, and I am having the most difficult time understanding what is driving the scheduling of tasks. 1 thing I have figured out is, that by adding a release date to a fixed version, issues in that version get scheduled within that time frame. But here is what I would like to know...

What about issues that are not in a fixed version?  For example, if I have an Epic that is not part of a fixed version, it has 10 stories that add up to 50pts.....how do I manage something like that? How is start date and end date determined for the epic?.....same for the underlying stories? I assumed due date would be the primary factor, but that doesn't seem to have any effect. Also, what if the work is still in my backlog (i.e. not in a created, future sprint)? 

Also...Im using v2.16 I believe...but its definitely not the newer interface. 

 

 

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events