Our users are planning their projects with Portfolio. But sometimes an Epic is not ready to be broken down in more specific activities such as asks, for example because it is an epic planned to start somehow 6 Months from now.
These empty epics will be defined in specific activities later on, when their activities are about to begin. Until then, our users wish to provide an epic estimate, so that their Portfolio can be drawn and estimates made.
When the epic is finally broken down into Tasks, their estimate would be replaced with the sum of the underlying items.
Currently we are running the default configuration for the "story points" custom field - so it is only available for Tasks and sub-tasks. The workaround the users adopted is to create a placeholder task just to give the epic an estimate (a task that will never be assigned, but deleted directly from the backlog!).
Also, they do not want to switch their portfolios into hours/days planning mode, as this would create double work (story points and estimates will both need to be filled).
One additional information is that of a organization-wide convention that says that 1 story point is (roughly) equal to 1 hour of work.
Question is: would you enable the story point field to epics or do you see drawbacks?
Thank you for your considerations!
