My ideas: Features

When you create or copy a feature, its ID is automatically created based on the product code. The ID is a combination of the product code and an auto number (and that is perfectly fine). But when you change the release reference to a release of an...

What is the challenge? Currently, on the Features board, if you sort features or epics within a release on the Start Date or Due Date, it is sorting the records with the earliest dates at the bottom. What is the impact? The records that will be st...

What is the challenge? Users have to open both the feature and the idea to see the votes and comments once an idea has been promoted What is the impact? Visibility/extra processes Describe your idea Idea votes and comments should cop...

What is the challenge? Teams today associate key results to Epics (you may call them features) and objectives to Programs (you may call them Programs) but are unable to view their key results as a contextual column in the epic prioritization view....

Would like to see an option in the account / workspace to only allow features to be associated with the same release as the epic.

What is the challenge? I use time in status a lot now that it is available. One thing I have had to create is multiple reports that show time in current status when looking at feature aging. I'd love to be able to display that on the card directly...

This would allow for an easy view that can be used to review and prioritize features, especially when features across multiple products have dependencies. Viewing and filtering multiple releases from different products in the same features board w...

Adding another feature request to gain visibility again to this needed enhancement. Our features board contains a combination of in-progress, scheduled and further out tentative / aspirational releases. We continually forget to change the release ...

What is the challenge? From a tool maintenance perspective, we have to individually maintain drop down values for similar fields. This presents problems with allowing for standard integration paths when different groups have their own field like...

What is the challenge? There are multiple ways to add attachments to ideas/features/epics. The only standard attachment field is on the description. When creating work requests, must move attachment to description to carry over. When integrating w...