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,556,448
Community Members
 
Community Events
184
Community Groups

How to account for waiting before starting a task (i.e. waiting for delivery of item)

In our team, sometimes we ship things between locations. I need the item to reach the destination before I can start working on tasks that involve that item (i.e. waiting for a circuit board to be delivered).

If I know delivery will take about 5 days, then I don't want any of the blocked tasks to start until 5 days from now. If the item DOES get delivered early, or there's a delay in delivery, I want to be able to see the effect of that.

I thought about setting up a "release" for when the item arrives. But then how do I dynamically control the beginning of work on the following release to coincide with the end of the current one? Otherwise I can set up a task for "waiting for delivery", however, this throws off the scheduler, because then I have a team member literally waiting around for a delivery rather than doing some other work in the meantime.

How do I make this work in Portfolio?

1 answer

1 accepted

0 votes
Answer accepted

To all future internet people, I found an answer but only in the Portfolio Server documentation. This will work great!

https://confluence.atlassian.com/jiraportfolioserver/time-constraints-715263082.html

Just in case that link goes dead, you are able to add an "Earliest Start Date" for an issue. So you either modify the "earliest start date" of whatever is being blocked, OR you can create a task for "delivery" and set its estimated time to 0 and adjust the "earliest start date" for it as you learn more about when it will arrive to have everything else schedule as portfolio does.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events