All ideas
Sort by:
Trending
Status:
Showing 8935
4
VOTE
Link user stories (requirements) in JIRA when under the same epic (feature)
We have features in Aha mapped to epics in JIRA, and then requirements mapped to user stories. I'd like the user stories in JIRA that I send over to automatically include links to their sister stories under the same epic, so that developers can ea...
2
Future consideration
2
VOTE
Block default customization from being modified
Anyone with customization permissions can modify the Default workflows, scorecards, time frames, etc. Without removing the option to set new default, why not blocking the default from being modified? this will allow an encourage users with the rig...
0
Future consideration
2
VOTE
Don't automatically open links in notes/descriptions in a new tab
When you try to open a link from a note/description in a new tab, some javascript automatically opens the link in a new tab and changes the focus to it. Opening a link in a new tab should be done in the background, like when done with the middle m...
0
Future consideration
5
VOTE
Allow "Predefined choice list" to select multiple items
Jira has the ability to have a custom field with selecting multiple items in a list. Aha can only support single items. The Aha multiple tags functionality is incompatible with Jira selects. We would like the ability to specify 2 or more items in ...
0
Unlikely to implement
1
VOTE
Manage external users to view presentations
We are looking to share a roadmap with external stakeholders from Aha. However, we want to control which external users can access in the case if an employee leaves on of our clients, we do not want them to retain access of our roadmap. Today, the...
1
Already exists
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
2
VOTE
Allow each team to provide an independent set of tags on a feature
Looking at the tags field on a develop feature, it inherits all of the tags from my main roadmaps workspace. This isn't the behaviour I'd expect, I would expect a develop team to have its own unique set of tags of primary relevance to them. In pla...
1
Future consideration
2
VOTE
Extend the 'Lock fields based on Status of the record' to Custom Tables
We use Custom Tables in many workspaces to track dollar savings.Once a project reaches a certain status these committed savings should be locked. It would be a great enhancement to be able to do this with Aha!'s 'Lock based on Status' functionality.
0
Future consideration
5
VOTE
Auto total of feature scores to be combined to create release score
Currently I am scoring at a feature level, and then having to go through and add up all of the feature scores to be able to get my release score populated. Ideally, it would be good if each scored feature could affect the release score automatical...
1
Already exists