The product would be more user friendly if you allowed users to interact with requirements in the same manner they can with features
What is the challenge?
Way too many clicks to set organize and manage requirements
What is the impact?
Extremely time consuming
Describe your idea
Introduce requirements cards. A user could then drag and drop them into features and r...
Guest
3 months ago
in Features
0
Likely to implement
Ability to create a set of todos or requirements based on a feature type
As a marketing team we often do the same things again and again. Currently, we have to use Podio to achieve the following.
For instance:
Creating a newsletter campaign requires the assigned person to do the following things and it's not ready unt...
Guest
almost 9 years ago
in Features
2
Already exists
Aha should delete the integration link when receiving a delete trigger from a webhook
We have Aha linked to JIRA. When we delete an issue in JIRA, this triggers our Webhook to send a message to Aha. I understand and agree that this should not cause Aha to delete the Feature connected to it for security reasons. But I would expect A...
Marvin van Dongen
over 9 years ago
in API / Features
8
Future consideration
Default view of Feature / Idea list for team members
You can currently customize your Feature / Idea list and save it. But there's no ability to set this customized view as the default for all team members. This would ensure everyone is looking at the same data with appropriate filters configured an...
Guest
over 6 years ago
in Features
0
Future consideration
Ability to tie color feature color to other fields
Status doesn't help to organize we would rather color code based on priority. We created a custom field for this and are eventually planning to use scorecards. We would like the ability to tie the color of the feature card to other fields beyond s...
Nick Galassi
almost 8 years ago
in Features
15
Future consideration
It would be great if, instead of just showing the underlying value, the scorecard metrics could use abstract labels... for example, for an 'effort' metric we might use t-shirt sizes such as "Small", "Medium", "Large" and "X-Large" behind the scene...
Guest
almost 10 years ago
in Features
6
Future consideration
We have a field that exists on both our Features and Requirements, and that custom field is being used in our JIRA integration. When creating a new requirement, it would be great to have the field auto-populate from what is specified in that field...
Guest
about 8 years ago
in Features
7
Future consideration
What is the challenge?
I want to add a category but I don't see any interface to do it and help search doesn't list anything related to categories
What is the impact?
I have ideas that are miscategorized or missing a category
Describ...
Guest
3 months ago
in Features / Ideas
1
Already exists
Rename product value field in non-product workspaces
The product value score terminology works well for workspaces where teams are building products. But in other workspaces it can be confusing. In these cases a more generic field name would be easier to understand.
Austin Merritt
over 3 years ago
in Features
2
Future consideration