My votes
Sort by:
Trending
Filter by:
Status
Showing 8992 of 8992
2
VOTE
Respect formatting in CSV import
I am importing a number of Features/Requirements from a CSV. There is a column for Description, which contains basic formatting (i.e. newlines, spaces). When this is imported all formatting is lost and it just becomes one long paragraph. I would l...
0
Unlikely to implement
1
VOTE
Email notifications alluding to the subject of the item not just the person
Right now, email notifications are presented in a "such-and-such created a to-do", this gives you no indication of what the to do is or why it is relevant, and thus makes it hard to separate the chaff from the wheat of Aha notifications
0
Future consideration
2
VOTE
Improve usability of features (and other) views
There is a usability problem when using the features view (and others also). If you select a product (with the product switcher), and look at a features view. Once you deselect some of the filters, it is not very clear anymore what you're actually...
0
Unlikely to implement
1
VOTE
Ability to remove stories that are in the integration from Aha!
Often times we only want a subset of what's in Aha! in our JIRA project. In some cases, when things get deprioritized, we want to remove them from JIRA but keep them in Aha! Would love the ability to do that FROM Aha! because keeping things in syn...
0
Future consideration
1
VOTE
1
VOTE
Provide a report to show required fields
As an admin, it would be helpful to have a report that would show all required fields by area - e.g. require fields for workspace, epic, feature, etc. and including workspace layout. This would help in the analysis of what fields are used and requ...
0
Future consideration
1
VOTE
1
VOTE
Deletion of Product Lines should not restructure permissions
When a product line is deleted and it's children are preserved, they are moved to the top-level instead of being inherited by the parent product line. This creates issues with permissions and it should not be so difficult to restructure the worksp...
0
Future consideration
1
VOTE
2
VOTE
Allow ability to mark a "To-Do" as "Unassigned" instead of defaulting to the user who wrote the Feature Card
As the Project Mgr for my Dev team, I oftentimes am the one driving the planning sessions and writing the Feature cards. Currently, any To-Dos written on a Feature Card are assigned to me automatically since I'm the one writing the card/to-do. I w...
2
Already exists