Allow diverse units for different estimate types

What is the challenge?

We do initial estimates for epics using time units, so that we can place those epics on the roadmap in Roadmaps workspaces using those estimates.

Once epics are broken down into stories and they are assigned to a team, we want to create detailed estimates in points for those stories.

The two types of estimates are done at different levels of granularity and for different purposes. There is no reason for them to be forced to use the same units.

What is the impact?

We cannot store time-based estimates within records at the workspace level and leverage them there. Estimation for sprints using points takes priority, so we can’t use the initial estimate field within roadmaps workspaces at all.

Describe your idea

Find a way to enable initial estimates for epics in roadmaps workspaces using an independent estimation unit from other estimate fields—could be independent based on record level, estimate field, or workspace type, or some combination of those things.

BTW, I don’t know anyone who estimates epics in points, so it doesn’t make much sense to force that if your related teams want to use points for detailed estimates.