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

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
4,559,582
Community Members
 
Community Events
184
Community Groups

How can I use portfolio with estimation of effort instead of story points?

Hello,

I am on a trial version of Portfolio. We usually use Kanban boards with release versions. Our due dates are based on the original estimates that are added by developers. My need is to be able to view the releases in the form of a project plan just like Portfolio displays them but nevertheless I could not.

 

I want to ask please where does the scheduled start come from? Why do issues extend along the timeline as a whole although I added a target start and a target end?

Moreover, is it possible for Portfolio to arrange the issues on the schedule based on the original estimate and according to the rank in the kanban without having to manually insert the start date and end date? This will make our day to day work much easier.

 

Thank  you

1 answer

1 vote
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 01, 2018

Hello Dima,

The Scheduling behavior comes from a few different locations for the calculation, and is covered in mode detail here:

https://confluence.atlassian.com/jiraportfolioserver/scheduling-behavior-802170552.html

 

The Placement of the issue in the timeline (Stretching across the timeline) is the calculated Scheduled start to end time.  The Target Start and Target End dates as apposed to the Scheduled Start and end dates are an indicator of planed vs actual the target being Planed and the Scheduled being based on calculations of the other inputs the actual amount that can be applied based on the variable inputs.  This will give you an indicator if a goal can be met or if you will come in under goal.

Additional details on the target Start and End dates is covered here:

https://confluence.atlassian.com/jiraportfoliocloud/add-target-start-and-target-end-dates-868977060.html

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events