Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Epic

Showing 163 of 9172

Dissociate Scorecards from Released Epics

When scorecards are applied to a product line, updates to the scorecard should not be applied to released epics. Since notifications for scorecard changes cannot be suppressed, changes to the scorecard result in a massive flood of email notificati...
Rachel Hiatt almost 4 years ago in Epic 0 Future consideration

Abandoning Epics

Despite your careful research, consideration, and planning - that epic you fought for inclusion into a release just isn't going to get started any time soon. Sprints later you realize that it's probably not going to happen ever. Holding on to hope...
Erik Didriksen over 5 years ago in Epic 0 Already exists

Change Master Feature Prefix

The Prefix for all Master Features is 'E', this is a suggestion to change this globally to M to align with the default terminology. EG PRODUCT-E-123 should be PRODUCT-M-123 instead.
Guest over 5 years ago in Epic 1 Unlikely to implement

data entered in multiple languages

Be able to enter data in multiple languages object references (Features, epic) Descriptions of objects Basic data
Guest almost 2 years ago in Epic 0 Future consideration

Branch Logic - Conditional Formatting of Forms

We have sophisticated intake requests for portfolio work for which we use at the Epic level. To streamline this for our team we would like to have one form where a user is guided through conditionally displayed questions based on previous question...
Guest about 4 years ago in Epic 1 Future consideration

Add the ability to customize Master Feature cards on the Master Features Road Map

The Master Features Road Map does a great job of showing what master features we are working on in each release and the why. The why being the goals and initiatives they support. Those releases are organized by external due dates and show nicely. ...
Guest over 6 years ago in Epic 0 Unlikely to implement

The History for linking and unlinking features to master features.

We need a way of identifying any scope creep by viewing the history of a master feature to see if any new features have been linked to it. This functionality is available at a feature level as you can see all requirements that are linked to it.
Guest over 6 years ago in Epic 0 Already exists

Limit Custom Fields Linked to Records Using Criteria

Ask : When creating a custom field related to a record (ex. Custom field showing all Epics from all other workspaces), I need a way to display only records that meet some criteria. Example of criteria would be: The records in a specific product li...
Mousa Mitwasi over 4 years ago in Epic 0 Future consideration

Filtering master features on feature roadmap

Under Reports / Roadmap / Features in customize view we select "show master features" as we want to show both master features and features we can add filter on feature tags : this works fine but if we add filter on master tags for e.g. : it isn't...
Agnes Muller over 6 years ago in Epic 0 Unlikely to implement

Ability to create epic/feature templates

In complex software development we often have features that require the coordination of changes across multiple software products. In these cases we create an Epic to represent the overall capability we wish to deliver, and place related features ...
Andrew Foster about 2 years ago in Epic 2 Future consideration