The Initial Estimate Field of Epics and Features allows breaking down the effort values by Team. However, the Detailed Estimate Field does not allow effort to be broken down by team. You can only enter a value, but you cannot assign it to a specif...
Valentina Morales
over 1 year ago
in Capacity planning
4
Future consideration
Who would benefit? Comments to an idea can be added by almost anyone, even if they are not the original owner of the idea, and even without admin permissions. So, if we enabled API search for comments, a non-admin user could add a searchable hasht...
Guest
about 1 year ago
in API
0
Future consideration
This would really help when capturing ideas on our ideas portal. I regularly have to review lengthy descriptions which have been added as ideas. I'd love to be able to restrict how many characters my users can type into 'description' fields, so th...
Steve Brunt
over 5 years ago
in Ideas portal
0
Unlikely to implement
What is the challenge? The snap feature for Aha! UML diagram should be more robust. Need for more UML templates. Export in more formats. Ability to develop Product report. What is the impact? The lack of a snap feature for some elements impacts th...
Guest
5 months ago
in Whiteboards
2
Future consideration
What is the challenge? we import releases from Github Milestones which have no start date meaning the date range on releases is incorrect. What is the impact? results in releases on roadmaps which have inaccurate (infinite) bars and require manual...
Guest
9 months ago
in Releases
0
Future consideration
This has been requested a number of times but I don't think it's been properly addressed. I don't want to assign some Ideas to a specific product. I want a Product Line to consider the idea. It could be a new Product, or a solution that spans prod...
Max Cascone
almost 8 years ago
in Ideas
0
Unlikely to implement
I am beginning to use the Whiteboard feature to map out the Objectives and Epics my Product Team plans to work on each Program Increment over time. I want to be able to link the stickies on the Whiteboard to actual existing Objective or Epic recor...
Justin Beardslee
about 2 years ago
in Whiteboards
5
Future consideration
Currently, as far as I am aware, the only way to use Components from Jira is to add a custom field in Aha! and map them. This works OK, however if a new component is added in Jira you have to manually add it to Aha! as an option to select. Please ...
Guest
almost 2 years ago
in Jira
0
Future consideration
Allow scorecards to be inherited from the product line
We have a lot of sub-products in our company, but we'd like to use the same general scorecard, linked to our general product goals, for all of them. It seems that currently scorecards need to be configured for each and every product, which isn't e...
Guest
about 8 years ago
in Account settings
1
Unlikely to implement
Support mapping Asset object fields through Jira integration
Who would benefit? Customers using the Asset object through Jira Service Management. What impact would it make? When these Asset fields are added to Jira issue screens, this would allow users to map these fields to Aha! fields through the Jira int...
Stephanie Lechner
about 1 year ago
in Jira
0
Future consideration