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
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
What is your goal in locking the epic down? Portfolio is built on top of Jira and is using agile methodologies for laying out the timeline based on the inputs of the issues.
In Agile methodologies Epics are intended to have issues added and removed over the lifespan of the epic, because epics are designed to last multiple sprints and spread across multiple projects, so translated to portfolio it would also be expected to have the schedule adjust as the epic progresses and scope change occurs. This is mentioned in:
Unlike sprints, scope change in epics is a natural aspect of agile development. Epics are almost always delivered over a set of sprints. As a team learns more about an epic through development and customer feedback, some user stories will be added and removed to optimize the team's release time.
Additionally with portfolio when scheduling the issue the forecast is expected to change and update based on additional inputs acquired over the course of a project as its looking at what can still be done in the project as time progresses and the variables are updated to reflect the current work stream of the project.