Skip to Main Content
ADD A NEW IDEA

Features

Showing 1151 of 8673

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...
Emily vargas about 6 years ago in Features 22 Unlikely to implement

Enable reporting & timeline dependencies from feature based on a work request

Who would benefit? Product Managers managing work in multiple workspaces with multiple teams What impact would it make? Enable teams to report out on timeline impacts for the feature/epic relationship as it crosses workspaces How should it work? A...
Steven Schafer 7 months ago in Features 3 Future consideration

Customize Default Fields on Records - Renaming and Adding Descriptions

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...
Ankar S about 3 years ago in Features 9 Future consideration

Allow the creation of to-dos in a custom "create new feature" template

You just launched a feature whereby you can create a list of to-dos in a feature, and then when you copy that feature the to-dos are copied over with them. However this is a very clumsy way to have to create new features every single time. I need ...
Guest about 7 years ago in Features 17 Future consideration

Inherit field values from Epics to Features

By default, have the Epic based data values copied over to the Feature data fields when the user creates a new feature from an epic card. This eliminates the need for re-entering and possibly inconsistent values for the same fields. If inherited f...
Guest about 3 years ago in Features 7 Future consideration

Add option to drive Feature progress % by the feature status

The progress % on a feature should be in sync with the status of the feature. When the status changes so should the progress %. Using to-dos, requirements, or estimates to drive the feature progress % isn't an option for us as different groups may...
Teresa Blok over 4 years ago in Features 17 Future consideration

Enable feature to belong to multiple workspace epics

Who would benefit? Product Managers managing features in epics to know where dependencies exist and updating timelines for the epic What impact would it make? Ensure the dependencies are shared/viewable in reporting outside the gantt chart view on...
Steven Schafer 7 months ago in Features 0 Future consideration

Capacity for teams: Estimate in skills

Capacity for teams currently allows you to create teams and add detailed estimates to records. However, we have a challenge with the way a team's capacity is calculated. We have cross-functional teams, which include people in product management, Q...
Nathaniel Collum about 4 years ago in Capacity planning / Features 2 Future consideration

Add custom filters to the Program Board

What is the challenge? Program Board lacks the same custom filters that are possible to select for Workspace Features Board What is the impact? Unable to filter on specific attributes of Features such as Feature Name, Name Search, Assigned etc Des...
David Winbanks about 1 month ago in Features 0 Future consideration

Capacity view is not flexible

Who would benefit? All team members as we use the velocity view for assignments and epic prioritization. What impact would it make? The view would be more realistic and not padded How should it work? Aha calculates used and available capacity for ...
Guest 7 months ago in Features 0 Future consideration