Using bulk edit to removed "assigned to" from the to-dos
I want to bulk edit to make the "Assigned to" as Unassigned. Since I'm the creator, the current bulk edit won't let me do that. Instead, it adds my name to all the to-dos.
Guest
about 6 years ago
in To-dos
6
Future consideration
Strategic models templates for Lean Product Canvas and Lean Strategy Canvas
What is the challenge? There's a new Lean Product Canvas and Lean Strategy Canvas posted by Jeff Gothelf. Here's a post with more. What is the impact? Teams using Aha! can create their own custom templates for Strategy > Models. Curious if thes...
Craig Pflumm
3 months ago
in Strategy
0
Future consideration
What is the challenge? When incident happens with software system, like to prepare a report which then can be promoted to work item What is the impact? Describe your idea Template for incident report
Guest
3 months ago
in Notes
0
Future consideration
Milestone Dates: Could we introduce a feature that retains the original milestone date, but also displays an arrow and a new icon when the date is changed?
What is the challenge? if the milestone date has changed, our team wants to be able to see both the old and new date. What is the impact? unable to see the date change when a project gets delayed Describe your idea have an icon for the original da...
Guest
3 months ago
in Features
0
Future consideration
Add dynamic idea submission forms to the Aha! side
What is the challenge? Currently, dynamic forms are only available within the portal. If team members are submitting ideas from within Aha!, they don't encounter the same logic. What is the impact? Streamline the idea submission configuration and ...
Becca Bommarito
7 months ago
in Ideas
0
Future consideration
I would like to be able to set the width for my public knowledge bases in bulk. This would be a HUGE time saver. It is extremely time consuming to edit notes to be “full width” one at a time if you did not notice this setting when first creating o...
Scott Goldblatt
7 months ago
in Knowledge base
0
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
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
In the old Aha! design there was an option on a feature to expand all the requirements. This was great for quickly showing all the links to Jira. Could you bring this option back?
Kelly Sebes
about 4 years ago
in Features
0
Future consideration
Rename product value field in non-product workspaces
The product value score terminology works well for workspaces where teams are building products. But in other workspaces it can be confusing. In these cases a more generic field name would be easier to understand.
Austin Merritt
almost 3 years ago
in Features
1
Future consideration