Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Features

Showing 1227 of 9560

"Type" field for Features shuold be optional

What is the challenge? The “Type” field is mandatory for Features but we don't have a use case for the field. What is the impact? The "Type" field is creating unnecessary noise on the screen every time a Feature request is submitted. D...
Guest 27 days ago in Features 0 Future consideration

Specify which fields will and will not be copied when copying a Feature

What is the challenge? When a Feature is copied, any field that is filled in will automatically be copied over to the newly created Feature What is the impact? Although most of time this is ok, some fields are Read-Only and therefore cannot be cle...
Guest 9 months ago in Features 1 Future consideration
121 VOTE

Updating a feature's dates should automatically adjust dates of features with downstream dependencies

What is the challenge? Managing sequential tasks with fixed date offsets can be cumbersome when date changes aren’t automatically applied to downstream dependencies. Currently, only changes made via drag-and-drop on the Releases Overview/Roadmap p...
Matt Case over 8 years ago in Features 11 Planning to implement

Prioritization report should support displaying strategy fields with multiple records (goals, objectives, key results)

What is the challenge? The prioritization report cannot display strategy fields tied to multiple records (like goals, objectives, and key results). What is the impact? Goals, objectives and key results are vital reference points when determining a...
Nathaniel Collum 9 months ago in Features 1 Future consideration

Add standard Key Results field on the create record view

What is the challenge? The standard Key Results field is available for use in the feature record view but is not available on the create pop-up. What is the impact? Users need to be able to identify the associated Key Results at the create step so...
Ashley Tierney about 1 year ago in Features 0 Likely to implement

Don't remove lane in feature board view once shipped

Currently when you ship a release the lane disappears from the feature board view. It would be great if instead of disappearing all together the lane was simply greyed out or marked as shipped. The feature board view is where we look to see what w...
Guest over 7 years ago in Features 28 Unlikely to implement

Add Automation Trigger "Is Blank"

What is the challenge? For data quality, we want to notify an Epic/Feature creator when then have forgotten to tie the record to an Initiative, Objective, or Key Result What is the impact? Work that should be tied to these is not visible, monitore...
Guest about 1 year ago in Features 0 Future consideration

Update sort logic on Features board when sorting by Start Date or Due Date

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...
Stephanie Lechner 4 months ago in Features 0 Likely to implement

Rename default fields

This applies to all records with required default fields, not just Features: I would like to be able to customize fields that are default/'out of the box' fields on records. Specifically, I would like to be able to rename and add descriptions (hov...
Guest over 4 years ago in Features / Ideas 13 Likely to implement

Dynamic inputs for automations

What is the challenge? I want to be able to refer to the content of a field so that I can use this in automations What is the impact? Will help increase automation and reduce effort, creating a sticker product Describe your idea NT use Aha for var...
Guest 3 months ago in Features 0 Future consideration