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.
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!
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.
Is there a way to enforce that a Stage must completed before the next Stage is being scheduled?
Edited
We want to create a roadmap for feature development with Portfolio. Our feature workflow is split into two phases/stages which have been set up in Portfolio:
Stage 1: Discovery (Skills: Design, UX)
Stage 2: Implementation (Skills: UI, Engineering)
The resources within the feature teams have the necessary skills assigned in the team view.
What Portfolio does, and I don't understand why, is splitting up the stages: a part of the first stage (Discovery) is scheduled for the first sprint, then a part of the second stage (Implementation) in the next sprint, followed by another work package for stage 1 and stage 2 in later sprints. (see image: stage 1 is red, stage 2 is blue).
Is there a way to enforce that stage 1 is completed before the next stage is being scheduled?
Thank you,
Mark
