Skip to Main Content

Share your product feedback

ADD A NEW IDEA

All ideas

Showing 9095

Allow for parent-child linking across Jira projects without using an integration template

Some organizations that use SAFe store high-level records in one Jira project and the tactical work in team-specific Jira projects. These are often integrated to the same Aha! workspace. Today, you have to use the same integration template in the ...
Emily Yankush over 1 year ago in Jira 0 Future consideration

Allow more than 20 panels to be added to a dashboard

We need a single view (dashboard) for all of the workspaces across our Aha! account. Because there is a limit of 20 panels, we've created a 'part 1' and 'part 2' for our leadership team to review.
Raja Shekher Kammara about 4 years ago in Reports 1 Future consideration

Add borders to images in notes

What is the challenge? Not being able to add borders to images in notes. What is the impact? Images with white backgrounds tend to blend into the app's background. Adding a border can help create a clear distinction and improve visual consistency....
Ali Pordeli 3 months ago in  0 Future consideration

Mapping dependencies

That we can only have End-to-Start Dependencies drawn is causing issues with our program Overviews. Our Managers are concerned by all of the red. Please enable us to also include Start-to-Start Dependencies, and Start-to-End Dependencies. If we ca...
Guest over 2 years ago in Features 4 Future consideration

Support new tasklist structure in Github

Github is adding functionality to extend how tasklists are used and increase tracking and linkages between items. The Aha integration should be capable of supporting this - particularly the linkages and tracking between related items https://docs....
Guest over 1 year ago in GitHub 3 Future consideration

Allow nesting of rollup releases

Rollup releases are very useful in organizations with complex and nested product lines and products. A top level product may have a V2.0 which is a rollup of three subsystems, a perfect use case of a rollup release. If each of the subsystems, in t...
Bastian Schoell over 2 years ago in Releases 3 Future consideration

Prevent users from inadvertently moving Features' workspace

Who would benefit? Our company's 750+ workspaces What impact would it make? If not resolved, this can cause damage, manual work to re-create Aha! <> Jira integrations, and work becoming out of sync between the two. How should it work? We oft...
Donald Hebert 12 months ago in Epic 0 Future consideration

Epic Roadmaps by Roll-up release

Who would benefit? Any customer who has a quarterly marketing release that impacts multiple products What impact would it make? this would allow us to have a single consolidated view across our products with a single reporting view so the entire b...
Rob S 12 months ago in Roadmaps 0 Future consideration

Feature IDs should change when moved from one workspace to another.

What is the challenge? Feature IDs do not get updated when moved from one workspace to another What is the impact? it is confusing to know where it actually belongs Describe your idea when moving an idea to another workspace/release, update the ID
Mary Daul 3 months ago in Features 0 Future consideration

In the Menu: Account Settings > Customizations > Statuses and workflows, show a list without having to scroll down many times to find the workflow names

What is the challenge? In the Menu: Account Settings > Customizations > Statuses and workflows, What can I do to show a list without having to scroll down many times to find the workflow names (See screenshot below). What is the impact? I ne...
Mike Jacobson 3 months ago in Account settings 0 Future consideration