Parent version mapped to 2 different releases - let user decide where to import
The same Jira version may be associated with releases from more than one Aha! workspace. This can happen when different products in Aha! are all being released together. When auto-import is enabled on the integrations and a new record is created i...
Mark Crowe
over 4 years ago
in Jira
0
Future consideration
Auto filter should remove workspaces that are moved out of product lines
It appears that when using the "auto-select" function, a report will maintain the workspace selections, even if workspaces are moved OUT from under the selected product line. It would be extremely helpful to improve the auto-select filter to only ...
Deanna Senaratne
about 2 years ago
in Reports
0
Future consideration
It would be great if each user on the idea portal had the option to rank the priority of their ideas with restrictions preventing them from marking everything as most important. Using this data you could provide a value to each idea prioritization...
Jessica Wagner
over 4 years ago
in Voting
0
Future consideration
Allow feature to be associated with more than one master feature
Some of the features we're developing will support more than one master features. Currently there is a limitation that a feature can support one and only one master feature. This falls short for us and doesn't allow us to see where investment in o...
Perri-Anne Sims
over 6 years ago
in Features
0
Unlikely to implement
Add the ability to combine fields with GitHub Integration
We need the ability to send more information from Aha to GitHub, this would include the Due Date. We need the ability to combine fields from Aha to a single GitHub Field. E.g. Send Title + Due Date in Aha to the Title Field in...
George Champlin-Scharff
over 6 years ago
in GitHub
0
Future consideration
Our teams are using tags heavily to add planning metadata to features. Over time, duplicate and mistyped tags are introduced which can cause confusion. At the moment, only those with admin access (one person within our organization) can clean up a...
Gordon Cloke
over 6 years ago
in Account settings
0
Unlikely to implement
We should be able to configure specific release statuses so that they're restricted, editable only by certain users or user groups.
We have a Program Management group which maintains an authoritative list of releases the product organization has c...
Guest
over 8 years ago
in Account settings
1
Unlikely to implement
Unlock Collaboration! Enhance Profiles for Meaningful Connections on the Idea Portal
Hi Ideas Portal Power Users, Many of us, myself included, have encountered situations where limitations in user profiles on the Idea Portal hinder collaboration and problem-solving. I've personally missed out on connecting with others who share my...
Mark Finnern
about 2 years ago
in Ideas portal
2
Future consideration
Share the list of value among different custom fields
We have some custom fields that are replicated for Epic, Feature and Requirement (e.g. Area Path for the integration with Azure DevOps). They have a long list of values we need to replicate and maintain three times instead of one. It would be perf...
Guest
over 4 years ago
in Account settings
0
Future consideration
When navigating in Aha or editing from any report, we will often click on a feature or initiative link and then click on the release or associated goal from within that view. It'd be great to be able to quickly "go back" without having to scour th...
Guest
over 8 years ago
in Application
2
Already exists