Idea Categories allow for a single choice in the ideas portal. But we need the ability to filter on two dimensions, for example by Category (reports, search tool, map, etc) and then by a Vertical custom field.
We're using a (value / estimate) method for determining the score of a feature. The division usually results in a decimal point (so one feature is a score of 3.1, another is 3.4). Right now, Ahah is turning both into a 3.
We'd like to be able to s...
Jason Slaughter
over 10 years ago
in FeaturesShipped
It would be useful to add conditions to the new automation rules feature to allow for more targeted behavior. For example in my internal ideas portal, I have an approval step in the ideas workflow between "needs review" and the next step in the pr...
Ronnie Merkel
about 6 years ago
in AutomationsShipped
Link "ideas" portal comments to promoted "features"
When one promotes an "idea" to a "feature", the comments for the "idea" remain in the "idea" and don't move to the "feature". It would be very helpful if the features from an "idea" would seamlessly be available in features (even if it were just a...
It would be an improvement to be able to define the fields that appear when creating a request. For example, I have added a custom field to tag the customers that have requested a feature. Currently I have to add a feature, then edit the field in ...
We need the ability to have one choice list field present a list of values that depend on a selection that was made in another choice list field in the same record.
For example, I might have a choice list field in an idea that asks the idea submi...
The ability to use the same filter more than once in advanced filters
It would be great to have the ability to use the same filter more than once when using advanced filter logic.
For example:I want to filter a set of features that all have the tag “Dashboard” but then a subgroup that DON’T have the tag “Admin”.
Support aggregating Features into Sprints - and pushing into JIRA as a SPRINT
We need to be able to manage our Features, grouping them into SPRINTS and then pushing the sprint and features into JIRA as a complete set, ie. creating the SPRINT and associated JIRA Tickets. Because the support for SPRINTS doesn't exist in Aha, ...
Cynthia Countouris
over 9 years ago
in JiraShipped
We have an internal technology group that releases core functionality that other products are dependent on. I need to be able to show that to the execs so they can visually understand one of the internal constraints of delivering the product.
This...