All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5973
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
3
VOTE
Some substance around idea categories
I have posted multiple times about the great feature of Ideas in Aha, in particular what you can do with them internally outside the external-facing portal (great feature in and of itself, too!).
I have been using idea categories a bit, but I'm f...
1
Future consideration
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
1
VOTE
Add user first name and last name fields to Get User API response
Currently Aha stores user first and last names. In the get user and list users REST API response objects, those fields are combined into one field: name. So John and Doe just get returned as John Doe. This causes problems when you have many differ...
0
Future consideration
1
VOTE
Ability to show more release details on the feature board
In the feature board view, the top of each release column shows very limited information today. Just release name, release date, and capacity. It would be useful to show more information about a particular release at the top of each release column...
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
Allow Timeframe to be used for filtering in Worksheet fields
As part of our maturity review we want to quickly understand if a particular workspace has planned their Initiatives and Goals in the current Timeframe (e.g. this year). To do this we'd like to create a worksheet on the workspace object, but the f...
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
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