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.
Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events