Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Features

Showing 1196

Assume one predefined tag is needed

In tag fields, trigger the list view of tags only after clicking within the field. If I need another tag, let me click the field again. Currently, the behavior assumes that if I choose one tag, I'll probably want more. I don't, but I have to click...
Tom Beck over 7 years ago in Features 0 Unlikely to implement

Ability to access individual weights for each score fact via API

My team does reporting out of Aha! and currently pulls out score & score_facts attached to features but is in need of the weighting applied to each score fact/category to come up with the overall score.
Guest almost 4 years ago in Features 0 Future consideration

Risks/Issues/Escalations?

If I have a dependency on the ghant chart, what happens when it is red? why is there not a blocker feature option (at the least) where are we tracking risks and issues and blockers?
Anna Maddox almost 4 years ago in Features 0 Already exists

Change the size of the created/assigned to user image on feature cards

The ability to add a user image onto feature cards is excellent but, for large organisations with many users, it can be difficult to differentiate between users when the image is small and multiple people may look similar. It would be great if the...
Justin Woods over 7 years ago in Features 0 Unlikely to implement

Add/Remove columns custom table view

When you view a Custom Table, by default all the columns are shown. That makes viewing the table difficult, I would like a way to Add/Remove columns that are displayed for a Custom Table
Guest over 7 years ago in Features 0 Future consideration

Collated features workspace

To be able to see features from different workspaces in 1 area that has drag and drop functionality. For example we have feature in workspaces called: game mechanics, live ops and so on... we have given a custom field to say which quarter these wi...
Guest almost 4 years ago in Features 0 Future consideration

Ability to add specific field from elements like feature (currently only defaults to feature name for example)

When adding other entities like scenarios to a feature, it is useful if we can associate a feature number rather than the feature name which is the default field when you use the many to many table
Arun Kalyanaraman over 7 years ago in Features 1 Already exists

Automatically include links in dependency vizualization

I love the visual dependency map. One enhancement I would like to see considered is that initiatives that have other initiatives roll up into them should show automatically in the dependency map even though an explicit "link" has not been establis...
Guest over 7 years ago in Dependencies / Features 0 Unlikely to implement

Apply estimates as completed work for features imported as "shipped"

Currently you can set capacity so that remaining estimates are applied as completed work when a feature is set as shipped. However, when importing from JIRA (or CSV) an imported feature to an active release that is marked as shipped does not apply...
Danny Archer almost 8 years ago in Features 0 Unlikely to implement

Attach files from a different ticket

Our workflow for UX designers is that we open TODO for them on a feature, and they attach UX assets to the TODO and not to the feature (to allow PMs to review before adding to the Feature which causes them to sync to Azure DevOps). It would be nic...
Tomer almost 4 years ago in Features 0 Future consideration