We need to query on a custom field, SF Account ID, on the Aha record, to determine if an account has already been created in Aha. Because we can't do this, we are constantly creating duplicate accounts in Aha that need to be manually removed.
Sara Olson
over 1 year ago
in API
2
Future consideration
It would be useful to be able to allocate to-dos to approval groups, where the task is assigned to multiple assignees, but only one approval is required. At present, a to-do can only be marked as complete when all assignees have completed it. An e...
Dale Potter
about 4 years ago
in To-dos
0
Future consideration
Ability to create parallel phases in a release template
When defining a release template, there are phases which happen at the same time i.e. Development phase lasting 5 days, after which two phases run in parallel. I have worked around this by adding negative numbers but this does not seem to very int...
Manesh Patel
about 4 years ago
in Releases
0
Future consideration
We have a lot of people with rights to create new products, but they are not always notifying me when they do so I can add them to the Ideas portal and certain reports. I need to be able setup a workflow to notify me when a new Product is setup so...
Guest
over 5 years ago
in Product
0
Future consideration
When deactivating a user provide links to access the integrations directly
Currently when deactivating a user, the warning message provides the list of integrations to see. It would be helpful if each of those were a clickable link to open the integration or a link to report to those integrations to view/open.
Chris Dauer
over 1 year ago
in
0
Future consideration
Ability to filter by 'inherited' in workspace settings report
When making changes to many workspaces at once - like a change of standards or following a reorg' - it's helpful only to report on workspaces where a setting is inherited. List reports include whether or not a setting is inherited but only as a te...
Steve Dagless
over 1 year ago
in Reports
0
Future consideration
Allow parking lot features and releases to not be sent to Jira
I use the parking lot to prepare for my upcoming releases thus the release name is not in Jira. These are also stories that do not need to be in Jira yet. With integration turned on I get an error every time I move a feature around in the parking ...
Kyle Cain
over 5 years ago
in Jira
1
Already exists
Adding features from initiatives or whole initaitves in the story map would make life a lot easier
you can add existing records from a releawse or by feature, but adding entire iniatives worth of features is not possible. It would be helpful to be able to do that
Guest
over 1 year ago
in User story map
0
Future consideration
Handling Use Case of Features Tied to Company Initiatives
Use case: I have a “Test Company Initiative” parent initiative (company level) with child initiatives. Features are linked to those child initiatives. However, there may be one-off features that ALSO need to tie to the parent initiative because th...
Guest
over 1 year ago
in Reports
0
Future consideration
Integrate existing FogBugz cases into Aha! as features (similar to JIRA 2way integration)
This will allow teams that use FogBugz to onboard to Aha! easier, without having to orphan FogBugz cases already entered that cannot speak back to Aha! through the current FogBugz integration.
amy kennedy
over 8 years ago
in
2
Future consideration