Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


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!


How to keep epics atomic in Portfolio

Having just started using Portfolio I find it incredibly confusing. We have a very small team and so it is unlikely that more than one single team member will ever work on a particular epic. What my Portfolio schedule is assuming is that a team member would be happy to context-switch from one epic to another according to Portfolio's inner algorithm. The result is that all the epics appear to run concurrently but take several years to complete.

Is there a way to treat epics as an atomic unit that must be completed before starting items in another epic?



1 answer

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

Hi Carl,

To schedule an issue so that it must be completed before another issue can start, what you are looking for are call Dependencies.

Setting up the dependencies is covered in here, and additional details on how the Dependencies effect the timeline is covered here

By default you will have the Blocks dependency set up tied to the Blocks / is blocked by issue links.  So as an example if Epic-1 Blocks Epic-2 then Epic-2 will not be scheduled to start until all the child issues in Epic-1 are complete and the epic itself is completed.



Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events