What is the challenge? |
We want to distinguish between Epics which end up in the product, and Enablers which are required to deliver the product but not a part of the product itself |
What is the impact? |
By not having a record type of Enabler, we cannot seperate the technical debt from the product development. We cannot forecast or plan the amount of time related to technical debt distinct from true product development. |
Describe your idea |
Create an Enabler record type that has the same functionality that is an Epic with features and stories. The work type allows us to differentiate Architecture, Infrastructure, Compliance, and Exploration work separate and distinct from product development |
Thank you for your idea. One way to handle this now would be to use feature types. While the record type would still be feature, you would be able to report specifically on new features vs enablers as needed. Given this capability we are unlikely to add a new record type. We hope you can understand.