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
about 1 year ago
in Epic
0
Future consideration
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
about 1 year ago
in Roadmaps
0
Future consideration
Once we have created a release and scoped all the items into it, it would be helpful if we could "soft lock" the features in that release. A soft lock could be an option on each release with a toggle and a message. Once the toggle is ON and a new ...
Guest
almost 9 years ago
in Releases
6
Unlikely to implement
Reports often get created at the root level when first starting use of Aha but over time multiple users require different report folders. Then you need to move reports into those new folders. There is no bulk move feature so it is a lot of effort ...
Dave Tucker
about 4 years ago
in Reports
0
Future consideration
To be able to easily move the features upwards in the User Story Map
When I work with the User Story Map (great tool by the way), I sometimes make mistakes. When that happens all my features ger scattered out in map height wise. Then it is a REALLY tedious work to collect them at the top level.
There should be a w...
Guest
over 5 years ago
in User story map
2
Future consideration
Project Management is hard. I occasionally find tasks that were scheduled on a later release, but ended up getting completed, possibly due to a duplicate task, or the dev team pulled in a task from a future release. This is a pain since I have no ...
Chris Waters
about 10 years ago
in
9
Unlikely to implement
Our marketing workspace has been around for a few years, and it has quite a few notes that are no longer relevant. Currently we nest notes under an "Archive" note, but that is not an elegant solution because we have to move them one at a time. It ...
Guest
over 5 years ago
in Notes
0
Future consideration
Work Requests should ignore/remove archived workspaces
What is the challenge? Work requests that were assigned to a workspace, that has later been archived before a workspace owner could respond, cannot currently be closed. These work requests will show a "[Hidden project]" in the Pending response. Wh...
David I.
3 months ago
in To-dos
0
Future consideration
Use a Single Meta/Data Worksheet to Generate Multiple Report Types and Add Directly to Panels Without Pre-Saving
What is the challenge? The current process of creating and managing multiple reports can lead to overcrowded workflows and inefficiencies when building a unified dashboard. Users face difficulties in seamlessly generating multiple reports and orga...
Basak B Klumph
3 months ago
in Features
0
Future consideration