Who would benefit? Everyone who uses the Research tab. What impact would it make? Add more research faster. ⚡️ How should it work? I find myself wanting to use the Research tab more, but a couple things slow me down: 1) It takes more clicks to add...
Rose Smith
12 months ago
in Features
0
Future consideration
Ability to resize the flyout that opens when we click on features or other records from reports/board
We use most of the tabs that appear on features and other records often and now with the introduction of the custom tabs, even more so. One issue is that when you click on the record, only 4 or 5 tabs appear, and you cannot resize the flyout and i...
Arun Kalyanaraman
almost 3 years ago
in Features
0
Future consideration
Here's what I think would be ideal for scorecards, using a RICE model: Allow the user to select a text value that corresponds to the numeric score. This will help consistency across users and projects. So that a score for "Reach" might be expresse...
Bjorn Aannestad
almost 3 years ago
in Features
3
Future consideration
when doing things like assigning a feature to an epic, or viewing epics on any of the boards, it would be extremely useful to be able to filter out or separate out shipped epics (like is one with shipped releases)
Guest
almost 5 years ago
in Features
0
Future consideration
Track features that moved out one release into the next
It would be really useful to track features that are prioritised into a release but then drop out, either going into a subsequent release or back into the backlog. Currently this is captured manually but features fall through the cracks when peopl...
Guest
almost 5 years ago
in Features
2
Future consideration
Can we add the "Products" field to this list of custom fields supported for integration?
We have created a custom field named "Product" which is of type "Products Field". In our Jira 2.0 integration, we want to map this field to a Jira field called "Component/s". We can see "Component/s" on the Jira side but the "Product" field is not...
Guest
almost 7 years ago
in Features
1
Already exists
Provide a Prioritization template to allow a product line or workspace to "fix" default columns for any new prioritization report
Allow a "default" set of columns to be defined for Epic and Feature Prioritization reports. For larger organizations where investments are evaluated in common way, a default view would ensure our teams are consistent in the way this information is...
Chris Lenzo
about 2 years ago
in Features
4
Future consideration
When you create a list of all features assigned to a release you can add the columns for the requirements, however these columns do not all come in the correct order and each requirement creates a new line for the feature. E.G. A feature with 4 re...
Guest
about 10 years ago
in Features
3
Already exists
Ability to bulk edit dependencies and other item relationships
We use AHA across multiple sub-businesses. Our sub-business relies on capabilities delivered by another sub-business. It'd be much more efficient to make sure dependencies are properly mapped if I could make multiple features depend on another fea...
Currently, anybody receiving a Campaign (Features) To-do notification receives it the day before and on the day the campaign task is due. The option to choose the frequency a person receives a notification, such as just on the due date, would be u...
Guest
about 7 years ago
in Features
1
Future consideration