My ideas: Epics

I would like to be able to configure so that the master features (MF) and features (F) follows the release date. This would be very helpful during sprint planning and replanning. The bulk editing is a work around, but still when you move around th...

I would like to be able to select/configure whether the time calculation for a Master Feature is manually or automatically set on product line/product level. Today the default is manual so to get a "live" view based on features each Master feature...

I would like the ability to mark a goal or initiative as complete/obsolete so that they are not available for selection on the Master Feature, Feature or Release. I know that you can do this via Archive, but the issue with this is on the reporting...

When editing the titles of master features (or I assume it applies to any item like features, initiatives, releases, etc), the text editor should display multiple lines instead of just one. For long titles, the one-line display results in having t...

I would like to be able to have the option to add the original estimate, remaining estimate, and logged time fields to my feature and master feature cards (just like how I can pull them into a pivot table). It is helpful to see the original estima...

Currently if you move a Master Feature to another release it will ask you if you want to move all of the non-shipped features. This enhancement request is asking to be able to checkbox select which features you want to move. See example, I would w...

Currently, the user can link a feature to a master feature by searching by feature id. However, the user is unable to link a master deature by searching by master feature id. This creates an inconsistent user experience

We use Master Features a few different ways: A group of related features A use case that requires work (features) from different products. A feature that will be implemented in different products at different times (each of those would be a fea...

We deliver customer solutions on top of our base product which often drive the development of (future) features in our base product. Because we have to manage these features separately as part of delivery of this customer "product", we then find w...

This is a spin-off to the ideas that request that "custom fields" be incorporate-able into a score. It would be great if it wasn't just hard-entered integers, but anything that could be counted. For example, we use a tag field to indicate which of...