It's currently possible to create a new release in a new workspace that is a copy of a release in another workspace, which will also copy all of the features within that release. If I need to copy a single feature to a new workspace, though, I hav...
Finn Meyer
over 2 years ago
in Features
1
Future consideration
To give a capability to add blank as a value for custom fields via CSV upload.
What is the challenge? Currently when doing a bulk update for a custom field if the data is already present and we need to update the field via with blanks. As of now this has to be done manually. What is the impact? It takes a huge time to do a m...
Guest
4 months ago
in Features
0
Future consideration
Make it easy to prioritize a body of work's child records
Who would benefit? Teams who need to ensure clear prioritization on the subtasks within a body of work. What impact would it make? Right now, the only way to filter, for example, the features prioritization page to a specific body of work, is usin...
Reilly O'Connor
about 1 year ago
in Features
0
Future consideration
Enhance approval API to allow approval group to be set
What is the challenge? Managing approvals across many features efficiently What is the impact? Without using approval groups we would need to update all feature's approvers each time someone joins or leaves an approving team Describe your idea I w...
Matthew Andrews
7 months ago
in API / Features
0
Future consideration
In the old Aha! design there was an option on a feature to expand all the requirements. This was great for quickly showing all the links to Jira. Could you bring this option back?
Kelly Sebes
over 4 years ago
in Features
0
Future consideration
A way to track your progress with meeting deadlines and how many times they are moved. This could be integrated with capacity planning, but per user. I would like to see my personal capacity across all features and To Dos and keep track of it. Thi...
Guest
almost 10 years ago
in Features
1
Unlikely to implement
Within a given product there can be different types of initiatives and features. Aha! supports the concept of feature types and allows templating of the description field by type. Would like to see an expansion of this concept to support configura...
Bonnie Trei
over 5 years ago
in Features
5
Future consideration
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
almost 3 years ago
in Features
1
Future consideration
Allow features to be grouped by epic in feature board and feature workflow
Currently, there is no grouping available in feature board. In feature workflow, it is possible to group by assignee. It would be great to be able to group both views by epic.
Joao Tornovsky
over 3 years ago
in Features
0
Future consideration
We regularly release features across Desktop, Web and Mobile which we have as separate products in aha. We would prefer to be able to have a feature which is linked across all products, as all are updated at the same time. We currently add feature...
John Hopkin
over 9 years ago
in Features
11
Unlikely to implement