All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5892
3
VOTE
Integration with JIRA needs better Error handling support
Aha! integration with JIRA does not notify users on errors that would have happened during the integration (i.e. push/pull). This keeps the users in dark on what would have gone wrong and requires manual intervention to detect errors.
1
Future consideration
2
VOTE
Log Effort - Allow the configuration of quick actions to log typical time spent
It is possible to configure quick status transitions which is a very nice and quick way to change the status of an item in Aha. It would be excellent to have the ability to quickly log a preset amount of effort against a task as well. This button ...
0
Future consideration
1
VOTE
Automation - Ability to Remove Dates
Presently, there is not a way for us to remove due dates (or start dates) on epics, etc using the automation functionality native to Aha! We would like to have this as an option in the case that we decide to shelve an epic for a later date we can ...
0
Future consideration
3
VOTE
Turn Requirements Into First-Class-Citizens / Independent Objects
Being the driving factors for any application development, I find doing requirements right to be rather mission critical to Aha itself.
For example, one symptom as to why this idea is even needed is reflected in the category listing of an idea suc...
2
Future consideration
1
VOTE
Color concepts in strategic roadmap by product
I really want to be able to use the strategic roadmap tool for multiple products, but I can't color concepts by product in this view like I can other reports/roadmaps. The only way to tell which product it is is by the title in light grey parenthe...
0
Future consideration
2
VOTE
Use different custom layouts depending on feature status
When a feature hasn't been started, I'm mostly concerned with planning and requirements. But once it's ready for deployment, I want to see fields about the associated PR and staging environment. I want Develop to let me specify which fields should...
0
Future consideration
1
VOTE
Delivery risks: allow me to choose any date field (standard or custom) to use for the delivery risk check
Delivery risks are calculated against the due date of epics and features. Requirements don't have due dates, so this risk check is not present. I see two use cases here: If I have custom date field on a requirement, it would be great to be able to...
0
Future consideration
2
VOTE
Develop an OSLC REST based connector for Aha!
We need to link Aha! Roadmap items to other items in Sparx EA (OSLC compliant) using ArchiMate 3.1 and an OSLC connector for Aha! will enable us to do that. This connector will also enable us to link Sparx EA ArchiMate 3.1 model elements such as s...
0
Future consideration
2
VOTE
New section under Strategy or Info for definitions/product functions.
Our Product has multiple functions/modules. With each module there are some terminologies and concepts that need to be defined. I can use notes to create a document but that that can get messy really quick. I see this area working similar to how P...
0
Future consideration
4
VOTE
Configure Filters - Change Arrangement of Fields
It would be useful to be able to change the order of filter fields when configuring filters. After adding filter criteria, especially over time, it can make sense to put the fields in a certain logical order. Having the ability to drag-n-drop the ...
0
Future consideration