Skip to Main Content
ADD A NEW IDEA

Epic

Showing 147

Multi-line text editing in Feature/Master Feature titles

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...
Guest over 5 years ago in Epic 0 Future consideration

Additional time fields for customizing record cards

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...
Guest over 5 years ago in Epic 1 Future consideration

Choose which non-shipped features move with a Master Feature

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...
Guest over 5 years ago in Epic 0 Future consideration

Copying an epic should also copy the associated Features.

Currently, if I want to copy a Master Feature, I must copy the Master Feature, then copy each associated Feature and map them to the Master Feature. This is time consuming and doesn't make a lot of sense.
doug evans over 5 years ago in Epic 8 Future consideration

Epic record link - search by ID

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
Keith Davenport over 5 years ago in Epic 3 Future consideration

Allow different types of Master Features

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...
Julia Doyle over 5 years ago in Epic 1 Future consideration

Sharing Master Features between Products

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...
Guest over 5 years ago in Epic 0 Already exists

allow a scorecard to count the number of tags in a field and incorporate that into the score

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...
Oleg Yazvin over 5 years ago in Epic 2 Future consideration

Allow Attachments to Cascade to Master Features and Features

There are supporting docs that get attached to initiatives that are useful at every level of the product definition. Instead of re-attaching a document to a Master Feature or a Feature, it would be helpful to allow Initiative Attachments to be "ap...
Guest over 5 years ago in Epic 0 Future consideration

Remove the Master Feature ID from Card View

The first thing you see on the feature when it is tied to a feature on the card view is the id number of the master feature which isn't particularly helpful and takes up a lot of real estate.
Nicole Hardin over 5 years ago in Epic 0 Future consideration